Search usages shows stale results after switching git branches

I have project with large codebase. Sometimes editor.action.referenceSearch.trigger does not show me all the results. When I search with regular grep - open this file - after this everything works fine. What is the workaround for it? #

[DanTup]

Yeah, I remember we did some investigation some time ago but never really got to the bottom of it. Something I’ve heard recently is that people sometimes get confused when they have a modified file open in VS Code and then do a git operation - VS Code shows no warning that the underlying file has changed until the user tries to save. This makes it easy to work with a stale file for a while in the editor and not really notice (it does have a dirty indicator, but with lots of tabs open this can quickly be off-screen).

I’m gonna close this for now, but if @Aetet is still seeing this one recent builds, we can re-open and look further.

[bwilkerson]

Given how long it’s been since we had a stable build, I’d want to see this reproduced under a recent bleeding edge (or maybe dev) build.

That said, I don’t remember any specific fixes. Server ought to be getting notified when files on disk are changed (via the watcher package) and updating itself accordingly. There has always been some set of conditions under which this doesn’t work correctly, but as far as I remember we’ve been unable to characterize those conditions. I know that git commands are often cited as the operation being performed when this happens, but I don’t know why they causes problems.