-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"is touching" reporting false negatives on tiny tests #719
Comments
After further testing, I think this is an existing issue that isn't specifically related to #557 or #624. In particular, I've tried this test project on many versions, going back into September, and I get "wrong" (always "false") results on all versions I've tested. Here's the test project I've been using, from @BryceLTaylor (rename to SB3): |
I found that if I save the staging project to my computer, then re-upload it to scratch.mit.edu, it also always shows false. And vice versa, if I save the scratch.mit.edu project to my computer, and re-upload it to staging, it also shows true when I'm over the dot. I think the two projects are different |
The two purple dot costumes do differ |
tangentially, what's up with those NaNs |
Thanks for figuring this out! Also: I feel like "what's up with those NaNs" is the topic about 90% of the time when NaN comes up in a conversation. |
I'm not sure how those costumes became different. I just downloaded the project from staging and uploaded it to production without changing it. |
Yeah - it seems possible that we have another bug in here related to costumes' bounds being slightly different on initial save vs. import & save again. Maybe the fix-up code that we run on import can cause small errors like this. |
Expected Behavior
is touching
tests should not depend on the size of the objects in question or the size of the stageActual Behavior
This project behaves differently on staging vs production:
As of this test, the two environments differ only by these two changes:
updateCPURenderAttributes
calls to where they're actually needed #624Steps to Reproduce
Actual behavior:
Operating System and Browser
Seems to affect multiple browsers but Windows Chrome is the most-confirmed case so far.
The text was updated successfully, but these errors were encountered: