Danny Tuppeny

> We should document that `sourceChange` can only be invoked once What about documenting that subsequent calls will always return the original result and caching it in a field? I...

> I'm not sure that's true. It sounds like the debugger can break things either way. You're right - if the debugger calls this early, it would break. I was...

> I think I filed a bug Ah yes, you did - it was https://github.com/dart-lang/sdk/issues/61866. I've closed that one since this one has some additional info. > it was hard...

I've not seen any other reports like this. 100% CPU certainly does not look healthy if it's persisting for a long period after initial analysis. @JonasJW a few questions: -...

@JonasJW thanks - the page I meant was the one marked "Timing" on the left. Can you also confirm whether you're using any analyzer plugins? A few comments above suggest...

> When I run `find . -type l -ls ` I get a long list of I suppose symlinks that probably just belong the the packages I use, for example:...

> In total there are over 550 symlinks. Does any of this sound problematic? Nothing above looks like an issue to me - the issue would be if the link...

> The `Dart: Only Analyze Projets With Open Files` was disabled. I'm trying to enable it to see it that improves it, I will update you on this. FWIW, my...

@JonasJW are you able to reproduce this issue with any public projects? It might be easier to narrow down with an instrumentation log, but that log will contain parts of...

@mraleph > due to a regression which accidentally snuck in when we changed how LSP is started Is this fixed now, or does something need updating in the LSP server?...