Constant Request textDocument/semanticTokens/range failed. error in vscode

[LiamMorrow]

G'day, I've been using the c# devkit extension in vscode and have noticed that when editing razor files it constantly shows errors as notifications, simply when navigating to any razor file.

Request textDocument/semanticTokens/range failed.

Logs

Details

[Error - 20:31:23] [LanguageServerHost] System.ArgumentException: Range={ Start={ Line=207, Character=17 }, End={ Line=260, Character=0 } }. text.Length=5758. text.Lines.Count=230 ---> System.ArgumentOutOfRangeException: The requested line number 260 must be less than the number of lines 230. (Parameter 'Line') at Microsoft.CodeAnalysis.Text.TextLineCollection.GetPosition(LinePosition position) in /_/src/Compilers/Core/Portable/Text/TextLineCollection.cs:line 67 at Microsoft.CodeAnalysis.Text.TextLineCollection.GetTextSpan(LinePositionSpan span) in /_/src/Compilers/Core/Portable/Text/TextLineCollection.cs:line 78 at Microsoft.CodeAnalysis.LanguageServer.ProtocolConversions.RangeToTextSpan(Range range, SourceText text) in /_/src/Features/LanguageServer/Protocol/Extensions/ProtocolConversions.cs:line 287 --- End of inner exception stack trace --- at Microsoft.CodeAnalysis.LanguageServer.ProtocolConversions.RangeToTextSpan(Range range, SourceText text) in /_/src/Features/LanguageServer/Protocol/Extensions/ProtocolConversions.cs:line 292 at Microsoft.CodeAnalysis.LanguageServer.Handler.SemanticTokens.SemanticTokensHelpers.ComputeSemanticTokensDataAsync(ClientCapabilities capabilities, Document document, Range[] ranges, ClassificationOptions options, CancellationToken cancellationToken) in /_/src/Features/LanguageServer/Protocol/Handler/SemanticTokens/SemanticTokensHelpers.cs:line 85 at Microsoft.CodeAnalysis.LanguageServer.Handler.SemanticTokens.SemanticTokensHelpers.HandleRequestHelperAsync(IGlobalOptionService globalOptions, SemanticTokensRefreshQueue semanticTokensRefreshQueue, Range[] ranges, RequestContext context, CancellationToken cancellationToken) in /_/src/Features/LanguageServer/Protocol/Handler/SemanticTokens/SemanticTokensHelpers.cs:line 50 at Microsoft.CodeAnalysis.LanguageServer.Handler.SemanticTokens.SemanticTokensRangeHandler.HandleRequestAsync(SemanticTokensRangeParams request, RequestContext context, CancellationToken cancellationToken) in /_/src/Features/LanguageServer/Protocol/Handler/SemanticTokens/SemanticTokensRangeHandler.cs:line 45 at Microsoft.CommonLanguageServerProtocol.Framework.QueueItem`3.StartRequestAsync(TRequestContext context, CancellationToken cancellationToken) [Error - 20:31:23] Request textDocument/semanticTokens/range failed. Message: Range={ Start={ Line=207, Character=17 }, End={ Line=260, Character=0 } }. text.Length=5758. text.Lines.Count=230 Code: -32000 [object Object]

Note this happens on both the current release, and the prerelease.

[LiamMorrow]

To be honest, I'm not too fazed about the intellisense and that not working. If there was a way to disable these error notifications (you can't disable errors notifications in VSCode without a CSS hack), or downlevel them to warning that'd be immediately much better for me

[davidwengier]

Also reported internally in https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1957989

[phil-allen-msft]

@LiamMorrow , we've recently made some changes that are in the C# Extension for VS Code version 2.22.5 related to the handling of the casing of paths; does that resolve this issue for you?

[lonix1]

I have this even without the c# devkit extension

[chandrashekharjoshi-abb]

This issue is extremly annoying, first of all intellisense doesn't work and on top of that notification keep popping even when we type a single word. Turn of notification also doesn't work.

[LiamMorrow]

@LiamMorrow , we've recently made some changes that are in the C# Extension for VS Code version 2.22.5 related to the handling of the casing of paths; does that resolve this issue for you?

Sorry for the delay @phil-allen-msft it's been a hectic couple of weeks as I'm moving rn.

Currently running v2.24.17 (prerelease) and I haven't seen the issue after a brief play around 🎉