Open RedCMD opened 2 months ago
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.88.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!
I do think the bot shouldn't be so sensitive
@hediet do you have any idea? @alexdima seems to be away
This is concerning, I see it being broken in your video. I wonder if the collapsed code blocks play a part here, in this case we make multiple requests to the TS language service, with different ranges here https://github.com/microsoft/vscode/blob/4af0c6a8f4e8b7ba223d27acd2d894a76a912a5e/src/vs/editor/contrib/semanticTokens/browser/viewportSemanticTokens.ts#L122-L124.
It is possible that either TS replies with different semantic tokens based on the ranges that we pass in or that we have some sort of bug in the SparseTokensStore
when combining their reply.
@RedCMD thanks for reporting this issue! I didn't manage to reproduce this though, even with having folded ranges. Does this consistently happen on the code you've shown? ~Do you mind sharing the code?~ Seems to be this code. Unfortunately, I still cannot reproduce.
I haven't been able to reproduce it since
if it does happen again is there anyway to get info about it without needing to restart?
I've had problems before where the folding ranges get out of sync with the document tho usually on large JSON files
Scrolling up and down causes semantic highlighting to randomly stop working
First time it's happened to me
I dare not restart anything atmtoo late 😔https://github.com/microsoft/vscode/assets/33529441/98184bfb-549f-4123-a810-1145060fb838
other files not affected its not locked to any certain scroll position (cut off points randomly shifts)
doesn't change 'while' scrolling, only after I've stopped scrolling for ~1sec
Somehow it still has its semantic token info applied
But isn't affecting '
dead
' code (darker blue). onlyconsts
possibly related: https://github.com/microsoft/vscode/issues/197459
don't know what extension caused this happened hours later