Ben Konyi
ad5133b373
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>
A package used to spawn the Dart Developer Service (DDS), which is used to communicate with a Dart VM Service instance and provide extended functionality to the core VM Service Protocol.
Functionality
Existing VM Service clients can issue both HTTP, websocket, and SSE requests to a running DDS instance as if it were an instance of the VM Service itself. If a request corresponds to an RPC defined in the VM Service Protocol, DDS will forward the request and return the response from the VM Service. Requests corresponding to an RPC defined in the DDS Protocol will be handled directly by the DDS instance.
SSE Support
For certain web clients it may be preferable or required to communicate with DDS using server-sent events (SSE). DDS has an SSE handler listening for requests on /$debugHandler.
SSE and package:vm_service example
import 'package:sse/sse.dart';
import 'package:vm_service/vm_service.dart';
void main() {
// Establish connection with DDS using SSE.
final ddsChannel = SseClient('${ddsUri}\$debugHandler');
// Wait for ddsChannel to be established
await ddsChannel.onOpen.first;
// Initialize VmService using the sink and stream from ddsChannel.
final vmService = VmService(
ddsChannel.stream,
(e) => ddsChannel.sink.add(e),
);
// You're ready to query DDS and the VM service!
print(await vmService.getVersion());
}