Danny Tuppeny

Thanks - I'm still not sure what's happening here. In your latest logs when running `flutter run --machine -v` I see the output end by printing an error and then...

Your latest log ends with what I'd expect for a normal termination - the debug adapter sends a `terminated` event: ``` [12:52:34 PM] [DAP] [Info]

Can you confirm how you installed Flutter? I suspect this isn't a VS Code issue (and you'd see the same running `flutter doctor` from the terminal), but it seems like...

Slightly related - VS Code allows us to provide some text/a command that can be shown at the bottom of the refactor list: https://github.com/microsoft/vscode/issues/86788  It's not per-action documentation, we...

This is tricky.. We only show it when the `service.reloadSources` service is available, however Flutter web pretends that Hot Reload is available and hot restarts. It would be better IMO...

I was only thinking about Flutter when I wrote the above, but now I'm wondering if we have a similar but slightly different issue for non-Flutter web, because the condition...

Given the work that's happening to support Hot Reload on Web (see https://docs.flutter.dev/platform-integration/web/building#hot-reload-web), I think this will become a non-issue, so I'm going to close this.

I've unfortunately not been able to reproduce this, and the LSP logs look normal (we send some diagnostics for that file during the branch switch, then we send an empty...

How can we help track down why we still see Problems from a file that's deleted and the extension has removed the diagnostics for? From the logs, it appears that...

> Maybe you can reproduce it this way? I couldn't, although we probably didn't test with the same file. Can you repro reliably? If you can on a public file,...