-
Notifications
You must be signed in to change notification settings - Fork 29.3k
[flutter_tools] remove flutter view cache #56223
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
[flutter_tools] remove flutter view cache #56223
Conversation
nvm, i misread the code, we waited forever lol. I wonder if instead we should wait for isolate runnable? Otherwise I could patch wait forever back in, seems bad to do polling if we don't need to. |
I think I don't quite follow, but waiting forever here sounds in line with the policy against timeouts. |
I added back the poll forever logic |
if (views.isNotEmpty || returnEarly) { | ||
return views; | ||
} | ||
await Future<void>.delayed(delay); |
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 previously had a 'This is taking a long time' message. Should that also be restored, or is this already wrapped in a status spinner thing?
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.
Ahh, status spinner is a good idea. Let me add that instead of adding a print
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.
Done
Status spinner added, tests updated - PTAL |
The Linux failure is a flake that I cannot rerun |
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, let's see if the attach test goes green.
This reverts commit 209bdcb.
Description
Fixes #56194
Remove caching of FlutterView. Perhaps the FlutterView RPC might return an empty list if the VM is not quite up yet? We had some old logic to poll the flutter views RPC for up to 200ms. That doesn't seem like a great approach, so instead we could forgo it entirely and trust that either the views come up before the developer tries to interact, or we crash.
https://github.com/flutter/flutter/blob/stable/packages/flutter_tools/lib/src/vmservice.dart#L1070