Danny Tuppeny

cross-origin-isolate is still gated with a flag in VS Code (so normal users can't get a wasm version), but if I: 1. Run `code --enable-coi` to enable cross-origin-isolate 2. Patch...

Ah, thanks for the pointer. I can just use the dev tools to see the network response - and it's a string:  Looks like this was actually fixed recently...

> Is there a way we can detect whether this is enabled, and fallback to using the dart2js version of DevTools if it is not? This already happens, because `window.crossOriginIsolated`...

But, I think we do need to add that extra header in to the DevTools server, otherwise I think we could load the WASM version but then fail with the...

@kenzieschmoll FYI, I did more testing of the wasm version in VS Code this morning, and I was unable to repro the performance issues I'd recalled (which we discussed a...

There are some possibly related issues here: - https://github.com/dart-lang/sdk/issues/55281 - https://github.com/dart-lang/sdk/issues/60335 Significantly, there was a regression in the latest SDK that could cause the analyzer to respond much more slowly...

@TheLastFlame were you able to browser the rest of the Analyzer diagnostic pages and only the report failed? If so, are you able to open developer tools for your browser...

> Even though my projects were on the Dev disk, Windows Defender still had an effect. If you didn't move your `.analysis-driver` folder also, then this could explain that. Most...

> I'm going to close this as a dupe of the upstream issue at https://github.com/dart-lang/sdk/issues/56755. Oops, I didn't realise this was already the SDK tracker and not Dart-Code, so it's...

> I understand that "latency" means the server is busy and can't start handling a request, is there any way to determine what it's busy doing? Latency here is the...