Konstantin Shcheglov
a8b48d3e2c
It caused race condition via async nature of DAS and AnalysisDriver. My understanding of the scenario: 1. We started fulling AD with files. 2. We set `priorityFiles`, this notifies the scheduler. 3. We add Dart files to AD. 4. We do something async, this allows the scheduler to ask AD to takes the next file, and start analyzing it. 5. We run transitionToAnalyzingToIdleIfNoFilesToAnalyze(), it sees there there are no files _to_ analyze (the only file is _being_ analyzed). So, it turns analysis on/off. 6. DAS sends "analysis: done", `dart analyze` says, I'm done, no errors. 7. AD ends analysis of the file, report errors. Too late. I believe we don't need this (hackish) method anymore. 1. We switch to analysis status with `priorityFiles`, for good or bad. 2. We are more aggressive now to switch status on/off. Bug: https://github.com/flutter/flutter/issues/141873 Change-Id: If4e8b74ebdce33b173a686a7b87d14368dfc175d Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/347421 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Konstantin Shcheglov <scheglov@google.com>
Package validation
The packages in pkg/ are automatically validated on the LUCI CI bots. The
validation is largely done by the tools/package_deps package; it can be tested
locally via:
dart tools/package_deps/bin/package_deps.dart
Packages which are published
There are several packages developed in pkg/ which are published to pub.
Validation of these packages is particularly important because the pub tools are
not used for these packages during development; we get our dependency versions
from the DEPS file. Its very easy for the dependencies specified in a package's
pubspec file to get out of date wrt the packages and versions actually used.
In order to better ensure we're publishing correct packages, we validate some properties of the pubspec files on our CI system. These validations include:
- that the dependencies listed in the pubspec are used in the package
- that all the packages used by the source are listed in the pubspec
- that we don't use relative path deps to pkg/ or third_party/ packages
Packages which are not published
For packages in pkg/ which we do not intend to be published, we put the following comment in the pubspec.yaml file:
# This package is not intended for consumption on pub.dev. DO NOT publish.
publish_to: none
These pubspecs are still validated by the package validation tool. The contents are more informational as the pubspecs for these packages are not consumed by the pub tool or ecosystem.
We validate:
- that the dependencies listed in the pubspec are used in the package
- that all the packages used by the source are listed in the pubspec
- that a reference to a pkg/ package is done via a relative path dependency