Create devcontainer.json

.cirrus.yml

@@ -1,50 +1,158 @@
-container:
-  image: cirrusci/flutter:base
+# CIRRUS CONFIGURATION FILE
+# https://cirrus-ci.org/guide/writing-tasks/
 
+environment:
+  # For details about environment variables used in Cirrus, including how encrypted variables work,
+  # see https://cirrus-ci.org/guide/writing-tasks/#environment-variables
+  # We change Flutter's directory to include a space in its name (see $CIRRUS_WORKING_DIR) so that
+  # we constantly test path names with spaces in them. The FLUTTER_SDK_PATH_WITH_SPACE variable must
+  # therefore have a space in it.
+  FLUTTER_SDK_PATH_WITH_SPACE: "flutter sdk"
+  # We force BOT to true so that all our tools know we're in a CI environment. This avoids any
+  # dependency on precisely how Cirrus is detected by our tools.
+  BOT: "true"
+
+gcp_credentials: ENCRYPTED[!ebad0a1f4f7a446b77944c33651460a7ab010b4617273cb016cf354eb8fc22aa92e37a3c58bfa4a0c40a799351e027a6!]
+
+# LINUX SHARDS
 task:
-  env:
-    CIRRUS_WORKING_DIR: "/tmp/flutter sdk"
+  gke_container:
+    dockerfile: "dev/ci/docker_linux/Dockerfile"
+    builder_image_name: docker-builder-linux # gce vm image
+    builder_image_project: flutter-cirrus
+    cluster_name: test-cluster
+    zone: us-central1-a
+    namespace: default
+    cpu: $CPU
+    memory: $MEMORY
+    use_in_memory_disk: $USE_IN_MEMORY_DISK
+  environment:
+    # We shrink our default resource requirement as much as possible because that way we are more
+    # likely to get scheduled. We require 4G of RAM because most of the shards (all but one as of
+    # October 2019) just get OOM-killed with less. Some shards may need more. When increasing the
+    # requirements for select shards, please leave a comment on those shards saying when you
+    # increased the requirements, what numbers you tried, and what the results were.
+    CPU: 1 # 0.1-8 without compute credits, 0.1-30 with (yes, you can go fractional)
+    MEMORY: 4G # 256M-24G without compute credits, 256M-90G with
+    CIRRUS_WORKING_DIR: "/tmp/$FLUTTER_SDK_PATH_WITH_SPACE"
+    CIRRUS_DOCKER_CONTEXT: "dev/"
     PATH: "$CIRRUS_WORKING_DIR/bin:$CIRRUS_WORKING_DIR/bin/cache/dart-sdk/bin:$PATH"
+    ANDROID_SDK_ROOT: "/opt/android_sdk"
+    SHOULD_UPDATE_PACKAGES: 'TRUE' # can be overridden at the task level
+    USE_IN_MEMORY_DISK: false
+  pub_cache:
+    folder: $HOME/.pub-cache
+    fingerprint_script: echo $OS; grep -r --include=pubspec.yaml 'PUBSPEC CHECKSUM' "$CIRRUS_WORKING_DIR"
+    reupload_on_changes: false
+  flutter_pkg_cache:
+    folder: bin/cache/pkg
+    fingerprint_script: echo $OS; cat bin/internal/*.version
+    reupload_on_changes: false
+  artifacts_cache:
+    folder: bin/cache/artifacts
+    fingerprint_script: echo $OS; cat bin/internal/*.version
+    reupload_on_changes: false
+  setup_script:
+    - date
+    - git clean -xffd --exclude=bin/cache/
+    - git fetch origin
+    - git fetch origin master # To set FETCH_HEAD, so that "git merge-base" works.
+    - flutter config --no-analytics
+    - if [ "$SHOULD_UPDATE_PACKAGES" == TRUE ]; then flutter update-packages; fi
+    - flutter doctor -v
+    - ./dev/bots/accept_android_sdk_licenses.sh
+    - date
+  on_failure:
+    failure_script:
+      - date
+      - which flutter
+  matrix:
+    - name: analyze-linux # linux-only
+      only_if: "$CIRRUS_PR != ''"
+      environment:
+        # Empirically, the analyze-linux shard runs surprisingly fast (under 15 minutes) with just 1
+        # CPU.  We noticed OOM failures with 6GB 4/2020, so we increased the memory.
+        CPU: 1
+        MEMORY: 8G
+      script:
+        - dart --enable-asserts ./dev/bots/analyze.dart
 
-  git_fetch_script: git fetch origin
-  setup_script: |
-    echo "SDK directory is: $PWD"
-    ./bin/flutter --version
+    - name: framework_tests-widgets-linux
+      only_if: "changesInclude('.cirrus.yml', 'dev/**', 'packages/flutter/**', 'packages/flutter_test/**', 'packages/flutter_tools/lib/src/test/**', 'bin/**') && $CIRRUS_PR != ''"
+      environment:
+        # We use 3 CPUs because that's the minimum required to get framework_tests-widgets-linux
+        # running fast enough that it is not the long pole, as of October 2019.
+        CPU: 3
+      script:
+        - dart --enable-asserts ./dev/bots/test.dart
 
-    # disable analytics on the bots and download Flutter dependencies
-    ./bin/flutter config --no-analytics
+    - name: framework_tests-libraries-linux
+      only_if: "changesInclude('.cirrus.yml', 'dev/**', 'packages/flutter/**', 'packages/flutter_test/**', 'packages/flutter_tools/lib/src/test/**', 'bin/**') && $CIRRUS_PR != ''"
+      environment:
+        # We use 3 CPUs because that's the minimum required to get the
+        # framework_tests-libraries-linux shard running fast enough that it is not the long pole, as
+        # of October 2019.
+        CPU: 3
+      script:
+        - dart --enable-asserts ./dev/bots/test.dart
 
-    # run pub get in all the repo packages
-    ./bin/flutter update-packages
+    - name: framework_tests-misc-linux
+      # this includes the tests for directories in dev/
+      only_if: "changesInclude('.cirrus.yml', 'dev/**', 'packages/flutter/**', 'packages/flutter_goldens/**', 'packages/flutter_test/**', 'packages/flutter_tools/lib/src/test/**', 'bin/**') && $CIRRUS_PR != ''"
+      environment:
+        # We use 3 CPUs because that's the minimum required to get framework_tests-misc-linux
+        # running fast enough that it is not the long pole, as of October 2019.
+        CPU: 3
+      script:
+        - dart --enable-asserts ./dev/bots/test.dart
 
-  matrix:
-    - name: docs
-      env:
-        SHARD: docs
-      docs_script: ./dev/bots/docs.sh
-    - name: analyze
-      env:
-        SHARD: analyze
-      test_script: dart ./dev/bots/test.dart
-    - name: tests-linux
-      env:
-        SHARD: tests
-      test_script: dart ./dev/bots/test.dart
-      container:
-        cpu: 4
-        memory: 8G
+    - name: tool_tests-general-linux
+      only_if: "changesInclude('.cirrus.yml', 'dev/**', 'packages/flutter_tools/**', 'bin/**') && $CIRRUS_PR != ''"
+      environment:
+        # As of November 2019, the tool_tests-general-linux shard got faster with more CPUs up to 4
+        # CPUs, and needed at least 10G of RAM to not run out of memory.
+        CPU: 4
+        MEMORY: 10G
+        SHOULD_UPDATE_PACKAGES: "FALSE"
+      script:
+        - (cd packages/flutter_tools; dart __deprecated_pub get)
+        - (cd packages/flutter_tools/test/data/asset_test/main; dart __deprecated_pub get)
+        - (cd packages/flutter_tools/test/data/asset_test/font; dart __deprecated_pub get)
+        - (cd dev/bots; dart __deprecated_pub get)
+        - dart --enable-asserts ./dev/bots/test.dart
 
-task:
-  name: tests-windows
-  env:
-    SHARD: tests
-  windows_container:
-    dockerfile: dev/bots/docker/Dockerfile.windows
-  env:
-    CIRRUS_WORKING_DIR: "C:\\Windows\\Temp\\flutter sdk"
-  git_fetch_script: git fetch origin
-  setup_script:
-    - bin\flutter.bat config --no-analytics
-    - bin\flutter.bat update-packages
-  test_all_script:
-    - bin\cache\dart-sdk\bin\dart.exe -c dev\bots\test.dart
+    - name: tool_tests-commands-linux
+      only_if: "changesInclude('.cirrus.yml', 'dev/**', 'packages/flutter_tools/**', 'bin/**') && $CIRRUS_PR != ''"
+      environment:
+        # As of October 2019, the tool_tests-commands-linux shard got faster with more CPUs up to 6
+        # CPUs, and needed at least 8G of RAM to not run out of memory.
+        # Increased to 10GB on 19th Nov 2019 due to significant number of OOMKilled failures on PR builds.
+        CPU: 6
+        MEMORY: 10G
+        SHOULD_UPDATE_PACKAGES: "FALSE"
+      script:
+        - (cd packages/flutter_tools; dart __deprecated_pub get)
+        - (cd dev/bots; dart __deprecated_pub get)
+        - dart --enable-asserts ./dev/bots/test.dart
+
+    - name: docs-linux # linux-only
+      environment:
+        CPU: 4
+        MEMORY: 12G
+      only_if: "$CIRRUS_PR != ''"
+      script:
+        - ./dev/bots/docs.sh
+
+    - name: customer_testing-linux
+      only_if: "$CIRRUS_PR != ''"
+      environment:
+        # Empirically, this shard runs fine at 1 CPU and 4G RAM as of October 2019. We will probably
+        # want to grow this container when we invite people to add their tests in large numbers.
+        SHOULD_UPDATE_PACKAGES: "FALSE"
+      script:
+        # Cirrus doesn't give us the master branch, so we have to fetch it for ourselves,
+        # otherwise we won't be able to figure out how old or new our current branch is.
+        - git config user.email "cirrus-bot@invalid"
+        - git fetch origin master:master
+        # The actual logic is in a shell script so that it can be shared between CIs.
+        - (cd dev/customer_testing/; ./ci.sh)

.devcontainer/devcontainer.json

@@ -0,0 +1,5 @@
+{
+  "image": "mcr.microsoft.com/devcontainers/universal:2",
+  "features": {
+  }
+}

.gitattributes

@@ -15,8 +15,17 @@
 *.yaml   text
 
 # Make sure that these Windows files always have CRLF line endings in checkout
-*.bat    text eol=crlf
-*.ps1    text eol=crlf
+*.bat             text eol=crlf
+*.ps1             text eol=crlf
+*.rc              text eol=crlf
+*.sln             text eol=crlf
+*.props           text eol=crlf
+*.vcxproj         text eol=crlf
+*.vcxproj.filters text eol=crlf
+# Including templatized versions.
+*.sln.tmpl        text eol=crlf
+*.props.tmpl      text eol=crlf
+*.vcxproj.tmpl    text eol=crlf
 
 # Never perform LF normalization on these files
 *.ico    binary

.github/ISSUE_TEMPLATE/1_activation.md

@@ -0,0 +1,53 @@
+---
+name: I am having difficulty installing Flutter or getting it to work
+about: You have run into problems while downloading or installing Flutter, or the
+  "flutter" tool is crashing, or you are running into some other issue before even
+  being able to use "flutter run".
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<!-- Thank you for using Flutter!
+
+     If you are looking for support, please check out our documentation
+     or consider asking a question on Stack Overflow:
+      * https://flutter.dev/
+      * https://api.flutter.dev/
+      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent
+
+     If you have found a bug or if our documentation doesn't have an answer
+     to what you're looking for, then fill out the template below. Please read
+     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
+-->
+
+## Steps to Reproduce
+
+<!-- Please tell us exactly how to reproduce the problem you are running into. -->
+
+1. ...
+2. ...
+3. ...
+
+## Logs
+
+<details>
+<summary>Logs</summary>
+
+<!--
+      Include the full logs of the commands you are running between the lines
+      with the backticks below. If you are running any "flutter" commands,
+      please include the output of running them with "--verbose"; for example,
+      the output of running "flutter --verbose create foo".
+-->
+
+```
+```
+
+<!-- If possible, paste the output of running `flutter doctor -v` here. -->
+
+```
+```
+
+</details>

.github/ISSUE_TEMPLATE/2_bug.md

@@ -0,0 +1,93 @@
+---
+name: I have a problem with my Flutter application.
+about: You are writing an application with Flutter but the application is crashing
+  or throws an exception, a widget is buggy, or something looks wrong.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<!-- Thank you for using Flutter!
+
+     If you are looking for support, please check out our documentation
+     or consider asking a question on Stack Overflow:
+      * https://flutter.dev/
+      * https://api.flutter.dev/
+      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent
+
+     If you have found a bug or if our documentation doesn't have an answer
+     to what you're looking for, then fill out the template below. Please read
+     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
+-->
+
+## Steps to Reproduce
+
+<!-- Please include full steps to reproduce so that we can reproduce the problem. -->
+
+1. Execute `flutter run` on the code sample <!-- (see "Code sample" section below) -->
+2. ... <!-- describe steps to demonstrate bug -->
+3. ... <!-- for example "Tap on X and see a crash" -->
+
+**Expected results:** <!-- what did you want to see? -->
+
+**Actual results:** <!-- what did you see? -->
+
+<details>
+<summary>Code sample</summary>
+
+<!--
+      Please create a minimal reproducible sample that shows the problem
+      and attach it below between the lines with the backticks.
+
+      To create it you can use `flutter create bug` command and update the `main.dart` file.
+
+      Alternatively, you can use https://dartpad.dev/
+      which is capable of creating and running small Flutter apps.
+
+      Without this we will unlikely be able to progress on the issue, and because of that
+      we regretfully will have to close it.
+-->
+
+```dart
+```
+
+</details>
+
+<details>
+  <summary>Logs</summary>
+
+<!--
+      Run your application with `flutter run --verbose` and attach all the
+      log output below between the lines with the backticks. If there is an
+      exception, please see if the error message includes enough information
+      to explain how to solve the issue. If there is a crash, please include
+      the entirety of the crash log including the backtrace.
+-->
+
+```
+```
+
+<!--
+     Run `flutter analyze` and attach any output of that command below.
+     If there are any analysis errors, try resolving them before filing this issue.
+-->
+
+```
+```
+
+<!-- Finally, paste the output of running `flutter doctor -v` here. -->
+
+```
+```
+
+</details>
+
+
+<!--
+      Consider also attaching screenshots and/or videos to better
+      illustrate the issue.
+
+      You can upload them directly on GitHub.
+      Beware that video file size is limited to 10MB.
+-->