[DDS] Fix server_connection_vm_service_test timeouts In `server_connection_common.dart`, the `server removes clients that disconnect from the API` test spawned its own Chrome instance using `package:devtools_shared`'s `Chrome` class without isolated profiles or essential headless flags. This caused the test to hang or fail flakily in container environments (like LUCI bots) and local environments: 1. Without `--use-mock-keychain`, headless Chrome on macOS blocks on system credential dialogs. 2. Without `--no-sandbox`, Chrome renderer processes can crash in restricted container environments. 3. Without `--user-data-dir`, Chrome uses the default system profile, which can cause it to attach to an existing open Chrome instance instead of starting a new one, meaning the process exits immediately and the test cannot terminate it. Fixed by directly using `package:browser_launcher`'s `Chrome` class in the test and passing: * `--user-data-dir` pointing to a unique temporary directory. * `--no-first-run` and `--no-default-browser-check` to bypass welcome prompts. * `--no-sandbox` and `--use-mock-keychain` where appropriate. Also wrapped the test in `try-finally` to guarantee cleanup of the temporary profile directory. Change-Id: I6fbe5a280524b57c635ab11ef54fa07dba2794cf Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/507600 Reviewed-by: Alexander Aprelev <aam@google.com> Auto-Submit: Ben Konyi <bkonyi@google.com> Commit-Queue: Ben Konyi <bkonyi@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.