1. 23 Jan, 2023 1 commit
  2. 12 Jan, 2023 1 commit
    • Andrew Kolos's avatar
      reduce pub output from flutter create (#118285) · ee1c59d4
      Andrew Kolos authored
      * reduce pub output from flutter create
      
      * fix fake Pub implementations
      
      * fix tests
      
      * Update pub.dart
      
      * replace enum with simpler boolean
      
      * fix tests
      
      * Revert "fix tests"
      
      This reverts commit 8a3182d3b95d4f2bf337343cdb76e88c2f428ca8.
      
      * Revert "replace enum with simpler boolean"
      
      This reverts commit 445dbc443db4eb5ce284f76749f60e81208b8783.
      
      * go back to using an enum
      ee1c59d4
  3. 10 Jan, 2023 1 commit
  4. 15 Dec, 2022 1 commit
  5. 06 Dec, 2022 1 commit
  6. 08 Nov, 2022 1 commit
  7. 04 Oct, 2022 1 commit
  8. 23 Sep, 2022 1 commit
  9. 08 Sep, 2022 1 commit
  10. 02 Sep, 2022 1 commit
  11. 29 Aug, 2022 2 commits
  12. 18 Aug, 2022 1 commit
  13. 26 Jul, 2022 1 commit
  14. 22 Jul, 2022 1 commit
    • Rich Kadel's avatar
      Remove outdated Fuchsia concepts (#107335) · 549f70c9
      Rich Kadel authored
      Fuchsia will soon remove all support for Component Framework version 1
      components (recognized by component manifests ending in `.cmx`).
      Notably, some of the `flutter` tool commands for Fuchsia devices--
      notably, but not limited to, those related to CFv1--are outdated, and
      either do not work today or soon won't work.
      
      This PR removes the outdated components and commands, replacing some
      with the newer version, or simply removing the non-working features,
      in some cases.
      549f70c9
  15. 18 Jul, 2022 1 commit
  16. 16 Jun, 2022 2 commits
  17. 15 Jun, 2022 1 commit
  18. 09 Jun, 2022 1 commit
  19. 25 May, 2022 2 commits
  20. 24 May, 2022 3 commits
  21. 17 May, 2022 2 commits
    • Chris Bracken's avatar
      [tool] Add tests for FakeProcess (#104013) · 9d9e272e
      Chris Bracken authored
      Because this class has some subtle behaviour with regards to control of
      exit timing and when and how it streams data to stderr and stdout, it's
      worth adding unit tests for this class directly, as well as (in a
      followup patch) for FakeProcessManager.
      
      This is additional testing relating to refactoring landed in:
      https://github.com/flutter/flutter/pull/103947
      
      Issue: https://github.com/flutter/flutter/issues/102451
      9d9e272e
    • Chris Bracken's avatar
      [tool] Consistent FakeProcessManager.run/runSync (#103947) · 928bb122
      Chris Bracken authored
      `FakeProcessManager` is a test-oriented implementation of `ProcessManager`
      that simulates launching processes and returning `ProcessResult` objects
      whose `exitCode`, `stdout`, `stderr` can be used to write platform-portable,
      hermetic tests that don't rely on actually launching processes from
      executables on disk. Its `run` and `runSync` methods provide asynchronous and
      synchronous variants of this functionality.
      
      Previously, the behaviour of `run` and `runSync` were inconsistent with
      regards to the treatment of the `stdoutEncoding` (similarly,
      `stderrEncoding`) parameters:
      
      `run`:
      * if the encoding was null, `ProcessResult.stdout` was returned as a
        String in UTF-8 encoding. This was incorrect. The behaviour as
        specified in `ProcessResult.stdout` is that in this case, a raw
        `List<int>` should be returned.
      * If the encoding was unspecified, `ProcessResult.stdout` was returned as
        a `String` in the `io.systemEncoding` encoding. This was correct.
      * If the encoding was non-null, `ProcessResult.stdout` was returned as a
        `String` in the specified encoding. This was correct.
      
      `runSync`:
      * if the encoding was null, `ProcessResult.stdout` was returned as a
        `List<int>` in UTF-8 encoding. This was incorrect. The behaviour as
        specified in `ProcessResult.stdout` is that in this case, a raw
        `List<int>` should be returned.
      * If the encoding was unspecified, `ProcessResult.stdout` was returned as
        `List<int>` in UTF-8 encoding. This was incorrect. The behaviour as
        specified in `ProcessResult.stdout` is that in this case, a String a
        `String` in the `io.systemEncoding` encoding should be returned.
      * if the encoding was non-null, `ProcessResult.stdout` was returned as a
        `String` in unknown (but probably UTF-8) encoding. This was incorrect.
        The behaviour as specified in `ProcessResult.stdout` is that in this
        case, a `String` in the specified encoding should be returned.
      
      `_FakeProcess`, from which we obtain the fake stdout and stderr values now
      holds these fields as raw `List<int>` of bytes rather than as `String`s. It
      is up to the user to supply values that can be decoded with the encoding
      passed to `run`/`runAsync`.
      
      `run` and `runAsync` have been updated to set stdout (likewise, stderr) as
      specified in the `ProcessResult` documentation.
      
      This is pre-factoring for #102451, in which the tool throws an exception
      when processing the JSON output from stdout of the `vswhere.exe` tool,
      whose output was found to include the `U+FFFD` Unicode replacement
      character during UTF-8 decoding, which triggers a `toolExit` exception
      when decoded using our [Utf8Decoder][decoder] configured with `reportErrors` =
      true. Because `FakeProcessManager.runAsync` did not previously invoke
      `utf8.decode` on its output (behaviour which differs from the non-fake
      implementation), it was impossible to write tests to verify the fix.
      
      Ref: https://api.flutter.dev/flutter/dart-io/ProcessResult/stdout.html
      
      Issue: https://github.com/flutter/flutter/issues/102451
      
      [decoder]: https://github.com/flutter/flutter/blob/fd312f1ccff909fde28d2247a489bf210bbc6c48/packages/flutter_tools/lib/src/convert.dart#L51-L60
      928bb122
  22. 07 May, 2022 1 commit
  23. 27 Apr, 2022 1 commit
  24. 26 Apr, 2022 1 commit
  25. 08 Apr, 2022 1 commit
  26. 31 Mar, 2022 1 commit
  27. 17 Mar, 2022 1 commit
  28. 09 Mar, 2022 1 commit
  29. 02 Mar, 2022 1 commit
  30. 25 Feb, 2022 1 commit
  31. 11 Feb, 2022 1 commit
  32. 02 Feb, 2022 2 commits
  33. 26 Jan, 2022 1 commit