Description
I have a long standing open issue in Dart-Code about using breaking on all exceptions. It seems to be quite common for people to enable this (in part, I think because Flutter catches exceptions and it's the only way to be able to examine state with the debugger), but when running tests there are a few places where exceptions are thrown during startup, for example:
To make things worse, VS Code doesn't handle this very well because there is no "user code" in the stack trace, so it doesn't know where to focus - so it doesn't focus anywhere. So what the user actually sees is:
I used to work around this by detecting Isolates that were the pub/test snapshots and never setting the exceptionPauseMode for them - however the names of isolates changed which broke that. I was able to re-do it using the isolateGroup names, however I discovered that the exception above is being thrown in the same isolate as the users test code, so that doesn't work either.
I don't have any great ideas for other fixes, so I'm wondering if it's possible to eliminate the exceptions that occur during startup here instead (the one in the screenshot above appears to be trying to parse <data:application/dart> as a URI)?