mirror of
https://github.com/flutter/flutter.git
synced 2026-02-20 02:29:02 +08:00
Registering the service worker immediately after the documented has loaded may cause SW initialization to compete with framework initialization. It was recommended to us that we defer the service worker setup until after the framework is done with setup, which should be sometime after the first frame. To implement this, I augmented the binding setup to dispatch an event on the document after the binding has initialized. I don't see any obvious risks with this setup. Fixes #66066
This directory contains tools and resources that the Flutter team uses during the development of the framework. The tools in this directory should not be necessary for developing Flutter applications, though of course, they may be interesting if you are curious.
The tests in this directory are run in the framework_tests_misc-*
shards.
Luci builder file
try_builders.json and prod_builders.json contain the supported luci
try/prod builders for flutter.
try_builders.json
It follows format:
{
"builders":[
{
"name":"yyy",
"repo":"flutter",
"taskName":"zzz",
"enabled":true,
"run_if":["a/b/", "c/d/**"]
}
]
}
- enabled(optional):
trueis the default value if unspecified - run_if(optional): will always be triggered if unspecified
prod_builders.json
It follows format:
{
"builders":[
{
"name":"yyy",
"repo":"flutter",
"taskName":"zzz",
"flaky":false
}
]
}
try_builders.json will be mainly used in
flutter/cocoon to trigger/update pre-submit
flutter luci tasks, whereas prod_builders.json will be mainly used in flutter/cocoon
to refresh luci task statuses to dashboard.