- 26 Oct, 2022 1 commit
-
-
Lucas Britto authored
-
- 24 Jun, 2022 1 commit
-
-
Jesús S Guerrero authored
-
- 31 Mar, 2022 1 commit
-
-
Michael Goderbauer authored
-
- 25 Jan, 2022 1 commit
-
-
Jesús S Guerrero authored
-
- 22 Dec, 2021 1 commit
-
-
Jenn Magder authored
-
- 30 Oct, 2021 1 commit
-
-
Christopher Fujino authored
-
- 18 Apr, 2021 1 commit
-
-
Jenn Magder authored
-
- 25 Mar, 2021 1 commit
-
-
Konstantin Scheglov authored
-
- 08 Feb, 2021 1 commit
-
-
Jonah Williams authored
This reverts commit 8b6baae4.
-
- 04 Feb, 2021 1 commit
-
-
Jonah Williams authored
Our current top crasher is an unclear error when ProcessManager fails to resolve an executable path. To fix this, we'd like to being adjusting the process resolution logic and adding more instrumentation to track failures. In order to begin the process, the ProcessManager has been folded back into the flutter tool
-
- 27 Jan, 2021 1 commit
-
-
Jonah Williams authored
* opt out the flutter tool * oops EOF * fix import * Update tool_backend.dart * Update daemon_client.dart * fix more
-
- 06 Nov, 2020 1 commit
-
-
Devon Carew authored
-
- 13 Oct, 2020 1 commit
-
-
Jonah Williams authored
Remove "This is taking a long time" progress timeout and TimeoutConfiguration.
-
- 02 Oct, 2020 1 commit
-
-
includecmath authored
No matter what level(error, warning, info) issues flutter analyze always return fatal exit code(1). CI/CD environment receive 1(!0). This may leads to e.g. Jenkins Build step 'Execute shell' marked build as failure. I propose according to AnalysisSeverity level return fatal(1) or success(0) exit code.
-
- 28 Jul, 2020 1 commit
-
-
includecmath authored
* Unified analyze error log format * Fix review issues
-
- 09 Jul, 2020 1 commit
-
-
includecmath authored
-
- 09 Jun, 2020 4 commits
-
-
Jonah Williams authored
flutter analyze was unconditionally using the cached dart-sdk for analysis, and was not running with the built SDK during local engine. This broke when trying to update the analyzer for null safety, since it required us to wait for the dart change to roll into the framework first.
-
Jonah Williams authored
This reverts commit 9ed3e5be.
-
Jonah Williams authored
flutter analyze was unconditionally using the cached dart-sdk for analysis, and was not running with the built SDK during local engine. This broke when trying to update the analyzer for null safety, since it required us to wait for the dart change to roll into the framework first.
-
Jenn Magder authored
-
- 14 May, 2020 1 commit
-
-
Zachary Anderson authored
-
- 06 May, 2020 1 commit
-
-
Zachary Anderson authored
-
- 22 Apr, 2020 1 commit
-
-
James D. Lin authored
Prefer using `.of()` (which is statically type-checked) over `.from()` (which is dynamically type-checked) when possible.
-
- 13 Apr, 2020 1 commit
-
-
Jonah Williams authored
-
- 06 Mar, 2020 1 commit
-
-
Jonah Williams authored
-
- 07 Jan, 2020 1 commit
-
-
Alexandre Ardhuin authored
-
- 06 Jan, 2020 1 commit
-
-
Jonah Williams authored
-
- 27 Nov, 2019 1 commit
-
-
Ian Hickson authored
* Update project.pbxproj files to say Flutter rather than Chromium Also, the templates now have an empty organization so that we don't cause people to give their apps a Flutter copyright. * Update the copyright notice checker to require a standard notice on all files * Update copyrights on Dart files. (This was a mechanical commit.) * Fix weird license headers on Dart files that deviate from our conventions; relicense Shrine. Some were already marked "The Flutter Authors", not clear why. Their dates have been normalized. Some were missing the blank line after the license. Some were randomly different in trivial ways for no apparent reason (e.g. missing the trailing period). * Clean up the copyrights in non-Dart files. (Manual edits.) Also, make sure templates don't have copyrights. * Fix some more ORGANIZATIONNAMEs
-
- 19 Nov, 2019 1 commit
-
-
Alexandre Ardhuin authored
* implicit-casts:false on flutter_tools/lib * address review comments * use castStringKeyedMap * introduce {bool,string,strings}Arg * fix ci
-
- 13 Sep, 2019 1 commit
-
-
Zachary Anderson authored
-
- 27 Mar, 2019 1 commit
-
-
Jonah Williams authored
-
- 11 Mar, 2019 1 commit
-
-
Paul Berry authored
Substantially reduces the danger that a bug in the analysis server might prevent errors from being detected by `flutter analyze`.
-
- 05 Feb, 2019 1 commit
-
-
xster authored
-
- 19 Jan, 2019 1 commit
-
-
Ian Hickson authored
These are essentially self-inflicted race conditions. Instead of timeouts we're going to try a more verbose logging mechanism that points out when things are taking a long time.
-
- 21 Dec, 2018 2 commits
-
-
Ian Hickson authored
This reverts commit 76f70810.
-
Ian Hickson authored
* Remove many timeouts. These are essentially self-inflicted race conditions. Instead of timeouts we're going to try a more verbose logging mechanism that points out when things are taking a long time. * Get the attach tests to pass. * Apply review comments from Todd * More review comment fixes * Put back the extended timeouts here now that I know why we have them...
-
- 19 Oct, 2018 3 commits
-
-
Devon Carew authored
-
Greg Spencer authored
Devon asked me to revert commit c4d1b31b. Merging on red to fix the build.
-
Devon Carew authored
* don't disable TODO issues in IDEs * minor change to start cirrus
-
- 11 Oct, 2018 1 commit
-
-
Greg Spencer authored
This attempts to re-land #22656. There are two changes from the original: I turned off wrapping completely when not sending output to a terminal. Previously I had defaulted to wrapping at and arbitrary 100 chars in that case, just to keep long messages from being too long, but that turns out the be a bad idea because there are tests that are relying on the specific form of the output. It's also pretty arbitrary, and mostly people sending output to a non-terminal will want unwrapped text. I found a better way to terminate ANSI color/bold sequences, so that they can be embedded within each other without needed quite as complex a dance with removing redundant sequences. As part of these changes, I removed the Logger.supportsColor setter so that the one source of truth for color support is in AnsiTerminal.supportsColor. * Turn on line wrapping again in usage and status messages, adds ANSI color to doctor and analysis messages. (#22656) This turns on text wrapping for usage messages and status messages. When on a terminal, wraps to the width of the terminal. When writing to a non-terminal, wrap lines at a default column width (currently defined to be 100 chars). If --no-wrap is specified, then no wrapping occurs. If --wrap-column is specified, wraps to that column (if --wrap is on). Adds ANSI color to the doctor and analysis output on terminals. This is in this PR with the wrapping, since wrapping needs to know how to count visible characters in the presence of ANSI sequences. (This is just one more step towards re-implementing all of Curses for Flutter. :-)) Will not print ANSI sequences when sent to a non-terminal, or of --no-color is specified. Fixes ANSI color and bold sequences so that they can be combined (bold, colored text), and a small bug in indentation calculation for wrapping. Since wrapping is now turned on, also removed many redundant '\n's in the code.
-