-
Notifications
You must be signed in to change notification settings - Fork 83
Save debug information in chrome.storage
after a Dart app loads
#1791
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
chrome.storage
after a Dart app loads chrome.storage
after a Dart app loads
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 with a comment.
final worker = (await serviceWorkerTarget.worker)!; | ||
// Note: The following delay is required to reduce flakiness (it makes | ||
// sure the execution context is ready): | ||
await Future.delayed(Duration(seconds: 1)); |
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.
Is 1 second enough time to guarantee that the context is ready, or should we try a few times? Btw, is there a way to reliably check that is ready?
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.
I ran this multiple times to confirm (same timeout as the other test case). I've moved the timeout itself into a const
variable for both so if we do end up changing it we can just change it in one place. When I first added this, I tried explicitly waiting on the worker's execution context, but that wasn't enough to prevent the flakes.
Uh oh!
There was an error while loading. Please reload this page.