Colen Garoutte-Carson

Hi @jmailloux . Just to confirm, here is what I am seeing with a very similar scenario: https://github.com/microsoft/vscode-cpptools/assets/49173979/7e0b10c1-06a4-48a0-a35e-c7a2ab23a81c I recorded that on Windows, but I repro similar behavior on macOS....

Hi @jmailloux . I'm having a difficult time reproducing the behavior you're seeing. I would expect to see the warnings you posted only if the compiler query succeeded (which it...

To investigate this, we could really use the debug output Sean asked for above. There are many things this could be. For instance, 1.19.4 made a database change, which will...

Hi @AndreGuimRua . Can you confirm what you're experiencing that is slower? Note that the `Update IntelliSense time (sec)` is the total time to update IntelliSense for the full file,...

Hi @Anguinru > When I talk about IntelliSense being slow, is >1 second (it wouldn't be an issue for me otherwise). By default, IntelliSense won't start updating within 1 second....

Hi @sangraamp . Since we're not tracking an issue blocking all Mac users, there may be something about your system or configuration that we may need to uncover to understand...

Hi @m76589 . Did your repro involve multiple workspace folders in a multi-root workspace that may have resolved to the same folder, due to a symbolic link in the file...

Hi @m76589 . To clarify, the issue we've identified is specific to _exactly_ the same 'workspace folder' being present multiple times in a multi-root workspace, at the root level. You...

> The compiler is not windows compatible. Hi @TracerDS . Do I understand correctly that you're using Windows, and not remoting into a WSL instance? If so, you're not going...

There are a few possible issues here. It's possible another IntelliSense operation was occurring, which can cause subsequent requests to our message handler (such as format on-type requests) to be...