-
Notifications
You must be signed in to change notification settings - Fork 27.3k
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 --no-sound-null-safety #3 #123297
[flutter_tools] Remove --no-sound-null-safety #3 #123297
Conversation
6b1c456
to
5ca3f42
Compare
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; waiting for cl/519269413
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
I updated this branch to try to get Google testing unstuck, but now two checks are failing on recently-added Clipboard.getData tests. I get the same failures when running on master (and even the commit that introduced the tests), which is weird because recent PRs have had these tests pass. Command I'm using to run the tests (from the packages/flutter directory): |
[flutter_tools] Remove --no-sound-null-safety #3
Re-land of flutter#123297 without any of the commits at the end attempting to fix customer-testing. Fixes flutter#118810
Part of #118837
Fixes #118810
The previous attempt, #123031, was reverted because some Google-specific workflows relied on being able to build non-null-safe apps.
This re-land leaves the top-level flag, while hiding it and throwing a tool exit if it ever used, unless a new context getter
globals.nonNullSafeBuilds
evaluates toNonNullSafeBuilds.notAllowed
, which will only be provided in Google-specific workflows.cl/519269413 is the internal fix that will override
globals.nonNullSafeBuilds
.