-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Suppress Flutter update check if --machine is present at all.
#150138
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
Suppress Flutter update check if --machine is present at all.
#150138
Conversation
andrewkolos
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 with uber-nits
| return super.run(args); | ||
| } | ||
|
|
||
| /// Whether to perform a flutter version check, which prints a warning if old. |
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.
Nit: Should a function's doc string explain (and thus be coupled to) what the caller(s) plan to do with it? (Not a big deal here since this comment is unlikely to become incorrect)
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
packages/flutter_tools/lib/src/runner/flutter_command_runner.dart
Outdated
Show resolved
Hide resolved
Update packages/flutter_tools/lib/src/runner/flutter_command_runner.dart Co-authored-by: Andrew Kolos <[email protected]> ++
272570b to
0250bae
Compare
|
auto label is removed for flutter/flutter/150138, due to - The status or check suite Mac tool_tests_general has failed. Please fix the issues identified (or deflake) before re-applying this label. |
|
auto label is removed for flutter/flutter/150138, due to - The status or check suite Linux analyze has failed. Please fix the issues identified (or deflake) before re-applying this label. |
|
auto label is removed for flutter/flutter/150138, due to - The status or check suite Google testing has failed. Please fix the issues identified (or deflake) before re-applying this label. |
flutter/flutter@01db23b...349ec71 2024-06-14 [email protected] Add tests for navigator.0.dart (flutter/flutter#150034) 2024-06-14 [email protected] Switch to `Iterable.cast` instance method (flutter/flutter#150185) 2024-06-14 [email protected] Include transform in static Gradient lerp methods (flutter/flutter#149624) 2024-06-14 [email protected] Validate the `contrastLevel` during `ColorScheme` creation (flutter/flutter#150176) 2024-06-14 49699333+dependabot[bot]@users.noreply.github.com Bump github/codeql-action from 3.25.9 to 3.25.10 (flutter/flutter#150228) 2024-06-13 [email protected] Fix leaky test. (flutter/flutter#150235) 2024-06-13 [email protected] Document CIPD role & login for upgrading Android engine (flutter/flutter#149433) 2024-06-13 [email protected] Update doc for `ColorScheme.surface` (flutter/flutter#150212) 2024-06-13 [email protected] Roll pub packages (flutter/flutter#150206) 2024-06-13 [email protected] Bump new release for a11y_assessment (flutter/flutter#150213) 2024-06-13 [email protected] Use --(no-)strip-wams instead of --(no-)-name-section in `dart compile wasm` (flutter/flutter#149641) 2024-06-13 [email protected] Reland "Identify and re-throw our dependency checking errors in flutter.groovy" (flutter/flutter#150128) 2024-06-13 [email protected] Use --(no-)strip-wams instead of --(no-)-name-section in `dart compile wasm` (flutter/flutter#150180) 2024-06-13 [email protected] Suppress Flutter update check if `--machine` is present at all. (flutter/flutter#150138) 2024-06-13 [email protected] [Reland] Introduce `ChipAnimationStyle` to override default chips animations durations (flutter/flutter#149876) 2024-06-13 [email protected] Update framework and flutter fix flutter.dev/docs links (flutter/flutter#150174) 2024-06-13 [email protected] Roll Flutter Engine from 4cb3025d3abf to 8167dffd1914 (2 revisions) (flutter/flutter#150208) 2024-06-13 [email protected] Replace InputDecorator M3 golden test (flutter/flutter#150111) 2024-06-13 [email protected] Roll Packages from 260102b to 7805455 (2 revisions) (flutter/flutter#150198) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages Please CC [email protected],[email protected],[email protected] on the revert to ensure that a human is aware of the problem. To file a bug in Packages: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
…ter#150138) Fixes flutter#145158. In an ideal world, the `--machine` flag would be strictly a global flag which sub-commands can choose to use (or perhaps just to report a `toolExit` that they don't have a `--machine` supported-mode if not. However currently, there is both a global flag, and command-specific flags. This leads to the confusing scenario where: ```sh flutter devices --machine ``` ... still checks for a Flutter update, printing a banner and breaking the JSON output. This PR "fixes" that by allowing `--machine` _anywhere_ in the command-line arguments to suppress the check. /cc @johnmccutchan.
…ter#150138) Fixes flutter#145158. In an ideal world, the `--machine` flag would be strictly a global flag which sub-commands can choose to use (or perhaps just to report a `toolExit` that they don't have a `--machine` supported-mode if not. However currently, there is both a global flag, and command-specific flags. This leads to the confusing scenario where: ```sh flutter devices --machine ``` ... still checks for a Flutter update, printing a banner and breaking the JSON output. This PR "fixes" that by allowing `--machine` _anywhere_ in the command-line arguments to suppress the check. /cc @johnmccutchan.
Was already fixed in flutter#150138, so removes duplicate flag. Already tested by existing test suite.
Was already fixed in flutter#150138, so removes duplicate flag. Already tested by existing test suite.
Was already fixed in flutter#150138, so removes duplicate flag. Already tested by existing test suite.
Was already fixed in flutter#150138, so removes duplicate flag. Already tested by existing test suite.
Was already fixed in flutter#150138, so removes duplicate flag. Already tested by existing test suite.
Fixes #145158.
In an ideal world, the
--machineflag would be strictly a global flag which sub-commands can choose to use (or perhaps just to report atoolExitthat they don't have a--machinesupported-mode if not. However currently, there is both a global flag, and command-specific flags.This leads to the confusing scenario where:
... still checks for a Flutter update, printing a banner and breaking the JSON output.
This PR "fixes" that by allowing
--machineanywhere in the command-line arguments to suppress the check./cc @johnmccutchan.