| commit | a16a6537e58d9faa7640bdd999834c6ccfff5f4a | [log] [tgz] |
|---|---|---|
| author | Ben Konyi <bkonyi@google.com> | Tue Jul 09 15:34:16 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 09 15:34:16 2024 +0000 |
| tree | 11006185af3d636b0b4b833999bee7d482c55f3e | |
| parent | 5e8ee777729a34187815465ad756079dbe6d601a [diff] |
Reland "Reapply "[ Service ] Start DDS and serve DevTools when the VM service is started via dart:developer"" This reverts commit 3370a4e3936d49090e176bd509ba5a1fed3b74d3. Reason for revert: Fixes landed in google3 (cl/650630536). Original change's description: > Revert "Reapply "[ Service ] Start DDS and serve DevTools when the VM service is started via dart:developer"" > > This reverts commit 44d44514761c06f201cf3d7277a558c5131e06e0. > > Reason for revert: b/350443042 > > Original change's description: > > Reapply "[ Service ] Start DDS and serve DevTools when the VM service is started via dart:developer" > > > > In the previous version of this change, if the user had 'dart' on their > > PATH and invoked 'dart compile js' (which spawns the VM service after > > compilation completes), the VM service would attempt to spawn DDS using > > './dart' as the executable path instead of 'dart'. This would result in > > DDS failing to start, causing the VM to print an error and hang. > > > > This updated change checks to see if the parent directory of > > `Platform.executable` is '.' and then verifies if './dart' exists or > > not. If it doesn't, 'dart' is likely on the user's PATH and should be > > used directly as the executable path. > > > > See https://github.com/dart-lang/sdk/issues/56087 for details. > > > > This reverts commit 4b88698e4814035a356e9f1a7e6b9a9167bfa94c. > > > > TEST=pkg/dds/test/control_web_server_starts_dds_with_dart_on_path_test.dart > > > > Change-Id: Id0f1dadd01d9202cbf7717f31393b43171cf3968 > > Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/373561 > > Auto-Submit: Ben Konyi <bkonyi@google.com> > > Reviewed-by: Derek Xu <derekx@google.com> > > Commit-Queue: Ben Konyi <bkonyi@google.com> > > Change-Id: I424c4b91b0b108ae4c9dffa0059ed90c918897e3 > Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/373744 > Reviewed-by: Siva Annamalai <asiva@google.com> > Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > Reviewed-by: Srujan Gaddam <srujzs@google.com> > Commit-Queue: Siva Annamalai <asiva@google.com> > Auto-Submit: Ivan Inozemtsev <iinozemtsev@google.com> Change-Id: Id7ddff5a80399203fb8058d84bc89fda2073da95 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/375000 Auto-Submit: Ben Konyi <bkonyi@google.com> Commit-Queue: Ben Konyi <bkonyi@google.com> Commit-Queue: Derek Xu <derekx@google.com> Reviewed-by: Derek Xu <derekx@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.