-
Notifications
You must be signed in to change notification settings - Fork 29.7k
[O] Removing all timeouts (mark II) #26736
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
|
cc @tvolkert Sorry this is a mess to review; I couldn't create new commits for most of the changes because they ended up being done as part of merges. |
726008b to
057e30e
Compare
tvolkert
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
* Remove many timeouts. These are essentially self-inflicted race conditions. Instead of timeouts we're going to try a more verbose logging mechanism that points out when things are taking a long time. * Get the attach tests to pass. * Apply review comments from Todd * More review comment fixes * Put back the extended timeouts here now that I know why we have them...
These are essentially self-inflicted race conditions. Instead of timeouts we're going to try a more verbose logging mechanism that points out when things are taking a long time.
| } | ||
| _log.trace('Waiting for service extension'); | ||
| // We will never receive the extension event if the user does not | ||
| // register it. If that happens, show a message but continue waiting. |
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.
This also means that if the flutter app crashed on startup we'll sit here forever.
Is there a way to handle that better?
I know that crashes are fairly rare and it may not be worth special casing them, just checking since I'm looking at one (#35890) right now.
No description provided.