Danny Tuppeny

I think you're seeing https://github.com/Dart-Code/Dart-Code/issues/4571 which was fixed via https://github.com/flutter/flutter/pull/131251 but was unfortunately after the cut for the last stable release. The fix should be in the Flutter beta branch...

Apparently I didn't look at your screenshots closely enough - I just noticed that the output here is not actually part of structured errors, so I'm less certain if the...

The reason you saw this in the pre-release and v3.72 and not in v3.70 is that in v3.72 (and the recent pre-releases) I increased the percentage of users that get...

Turns out there are two issues here: 1. We don't perform stack trace parsing on stdout output (only known errors) 2. The new debug adapters use `package:stack_trace` to parse stack...

The "trick" doesn't work on the new SDK DAPs. Tanthus was printing stack traces so they were in the format that the old debug adapters detected as stack traces and...

@martinsellergren real errors are when there is an exception that is unhandled (so is printed to stderr by Dart) or handled by Flutter (which triggers a "structured error"). If you're...

> How can we transform a `print(s)` to stderr, or whatever is required to be interpreted as a stack? For a Dart application, you could use `stderr.write`/`stderr.writeln` to write directly...

@adrianvintu > Some workaround? This is how we catch errors: I don't have any good workaround (besides using legacy adapters, but that's not great), but if you only need `Sentry`...

The rendering of markdown in the editor is handled by VS Code and themes, not the extension. While we can mark parts of the comments with specific tokens, how those...

> There was an issue https://github.com/Dart-Code/Dart-Code/issues/2670 about this issue before but it died off. I think the request there was a little different - it was to be able to...