-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Labels
P1A high priority bug; for example, a single project is unusable or has many test failuresA high priority bug; for example, a single project is unusable or has many test failuresdevexp-serverIssues related to some aspect of the analysis serverIssues related to some aspect of the analysis serverlegacy-area-analyzerUse area-devexp instead.Use area-devexp instead.type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)Incorrect behavior (everything from a crash to more subtle misbehavior)
Description
I recently rebuilt my analysis server. Previously I was running the version from 1e624b8; now I'm running the version from c549a73.
I'm noticing that the "show all symbols" command in VSCode no longer reliably shows me results. If I search for a class that I'm certain exists, about half the time I simply see "no matching workspace symbols".
I don't have repro steps, but here's an interesting clue: I just checked out a branch in which I know I have a method somewhere whose name starts with solo_. I triggered "show all symbols" and typed solo_, and as I was typing, I briefly saw the method I was looking for. But when I typed the final _, the result disappeared. Then I hit backspace to discard the final _, and the result appeared again.
Metadata
Metadata
Assignees
Labels
P1A high priority bug; for example, a single project is unusable or has many test failuresA high priority bug; for example, a single project is unusable or has many test failuresdevexp-serverIssues related to some aspect of the analysis serverIssues related to some aspect of the analysis serverlegacy-area-analyzerUse area-devexp instead.Use area-devexp instead.type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)Incorrect behavior (everything from a crash to more subtle misbehavior)