-
Notifications
You must be signed in to change notification settings - Fork 103
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
Avoid completing a non-nullable Completer with a nullable value #3328
Conversation
Ping for a review; I believe the test failures are unrelated. |
Is there any way to force merge past the existing breakage? I don't have the right authority, maybe? |
Unfortunately, cocoon is not allowed with a force merge. Seems some issue with some package versions: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8761714141529130593/+/u/dashboard/stdout. |
I can also disable the cocooon flutter customer tests until cocoon is back in a good state. |
@srawlins the issue is fixed at head (based on https://flutter-dashboard.appspot.com/#/build?repo=cocoon&branch=main). Can you rebase your branch? @keyonghan can we enable the "update branch" GitHub UI for Cocoon? |
That should be helpful. Filed flutter/flutter#140167 to track. |
Thanks everyone! Let's merge! 😁 |
Same as other repos, we use |
Implicitly passing a nullable value to a Completer of a non-nullable type can lead to surprising null-asserting exceptions. See dart-lang/sdk#53253 for more details. In this PR, we add an explicit null-assertion, which makes this call in-line with the general concepts of null safety.
Fixes flutter/flutter#137294
Pre-launch Checklist
///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.