| commit | 006751327d8756f6e227df24a8c8a288ddd7e2cc | [log] [tgz] |
|---|---|---|
| author | Sam Rawlins <srawlins@google.com> | Fri Oct 03 08:48:39 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 03 08:48:39 2025 -0700 |
| tree | 1285b065f69b960959e8c8d394d84998053420c2 | |
| parent | dc8b8fe072ba5e873679904acaa87c8b11bbc6e1 [diff] |
DAS plugins: properly throw and catch when a plugin cannot start I noticed, when running `dart analyze`, that when `pub upgrade` could not be run in a plugin directory, we would get the "An error occurred while setting up ..." message (good), but then the plugin would still be executed! And this message would get printed: > An unexpected error was encountered by the Analysis Server. > Please file an issue at https://github.com/dart-lang/sdk/issues/new/choose with the following details: > > Internal error: Issue stopping a plugin > Bad state: Cannot stop a plugin that is not running. The reason is that a PluginException was _only_ thrown, on line 560, if the package config file was still _missing_. But in my case, the plugin directory was pre-existing, from an earlier, successful run, and so the package config file existed! So no exception was thrown, and the server still attempted to run the plugin. So this CL makes that whole situation much simpler, and in particular removes the erroneous "An unexpected error was encountered by the Analysis Server" message that we do not want to show to users, and an extra stack trace. Change-Id: I9be39d10b687e055392f9b81285c99cca4c57534 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/453140 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Samuel Rawlins <srawlins@google.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.