dart-sdk/pkg/dds
Danny Tuppeny 793755f2c1 [dds/dap] Don't show stack traces in error messages from DAP
We accidentally started showing the stack traces in all errors rendered in VS Code. This changes the format of the message to not include the stack - although it keeps it in the payload to aid debugging when capturing logs.

It also slightly tweaks the error message for global eval to be less cryptic for VS Code.

Fixes https://github.com/Dart-Code/Dart-Code/issues/4899

Change-Id: Id4a0c4e6ef26065059e3becec62bab5d873e7be3
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/342621
Reviewed-by: Ben Konyi <bkonyi@google.com>
Reviewed-by: Helin Shiah <helinx@google.com>
2024-01-03 20:48:29 +00:00
..
bin Reland "[ Service / DDS ] Remove VM service polling logic, add --enable-service-fallback-port support to DDS" 2022-03-15 18:14:42 +00:00
example
lib [dds/dap] Don't show stack traces in error messages from DAP 2024-01-03 20:48:29 +00:00
test [dds/dap] Don't show stack traces in error messages from DAP 2024-01-03 20:48:29 +00:00
tool [dds/dap] Improve stack frame rendering + fix bad paths in tests 2023-07-06 15:01:21 +00:00
.gitignore
analysis_options.yaml [pkg] remove duplicate config from the analysis options files 2023-11-14 00:37:53 +00:00
CHANGELOG.md [dds/dap] Don't show stack traces in error messages from DAP 2024-01-03 20:48:29 +00:00
dds_protocol.md Add postEvent to dds client. 2023-06-02 19:07:39 +00:00
LICENSE
OWNERS [infra] Add OWNERS to the Dart SDK 2022-02-14 14:06:34 +00:00
pubspec.yaml Improve error handling for serving static DevTools assets. 2023-12-20 21:07:39 +00:00
README.md Improve error handling for serving static DevTools assets. 2023-12-20 21:07:39 +00:00

pub package package publisher

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());
}

Debugging DDS

One way to get stdout from files in DDS while debugging is to log messages to a file. You can add a method such as:

void _fileLog(String message) {
  final file = File('/tmp/dds.log');
  if (!file.existsSync()) {
    file.createSync();
  }
  file.writeAsStringSync(
'''
$message
''',
    mode: FileMode.append,
  );
}

Then you can call _fileLog('some print debugging message'), and the log message will be written to a temp file.

To get logging output in real time, run tail -f /tmp/dds.log.