-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Fix Image's logical flow which disposes its image too early, causing errors such as "Cannot clone a disposed image" #110131
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
Conversation
|
The test, without the fix, fails. This verifies the PR is needed. |
dnfield
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change makes sense to me and I think it's the right one. Thanks for doing some hard work here!
There are no expectations in the test that actually tell us whether the images ever actually complete, and its currently depending on some implementation details like RawImage being wrapped in a Semantics or being in the tree for this at all. Someone refactoring that code may easily misunderstand that this test actually is using those details to find the image.
It would be better to have a test that asserts we've done something meaningful as well. For example, someone could introduce a breakage to what you're fixing in the future where the second image never loads or the expected build order does not happen and this test would still pass.
I'd like to see the test not use any while loops, and have some more expectations about what's happening. Happy to chat some more about how to do this if it's not clear.
|
LGTM once tests are passing :) |
|
@dnfield Tests are passing :) |
|
What should I do now 👀 |
|
Sorry, thought I had added the label! |
|
|
Validations Fail. |
|
@dnfield That's OK. Oops seems to need one more reviewer |
goderbauer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…causing errors such as "Cannot clone a disposed image" (flutter/flutter#110131)
…causing errors such as "Cannot clone a disposed image" (flutter/flutter#110131)
…causing errors such as "Cannot clone a disposed image" (flutter/flutter#110131)
…causing errors such as "Cannot clone a disposed image" (flutter/flutter#110131)
…causing errors such as "Cannot clone a disposed image" (flutter/flutter#110131)
…causing errors such as "Cannot clone a disposed image" (flutter/flutter#110131)
…causing errors such as "Cannot clone a disposed image" (flutter/flutter#110131)
…causing errors such as "Cannot clone a disposed image" (flutter/flutter#110131)
…causing errors such as "Cannot clone a disposed image" (flutter/flutter#110131)
…causing errors such as "Cannot clone a disposed image" (flutter/flutter#110131)
…causing errors such as "Cannot clone a disposed image" (flutter/flutter#110131)
…causing errors such as "Cannot clone a disposed image" (flutter/flutter#110131)
* Migrate to Flutter 3.10.0 and Dart 3.0.0 (#557,#563,#570,#572,#573) * Cherry Pick flutter/flutter#110131 * Cherry Pick flutter/flutter#119495
* Cherry Pick flutter/flutter#110131 * Cherry Pick flutter/flutter#119495


Close #110129
Please see the issue for paragraphs about the bug cause and fix etc
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.