-
Notifications
You must be signed in to change notification settings - Fork 684
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C# extension continuosly errors while viewing/scrolling a diff of two csharp files. #6256
Comments
Looks like we're erroring creating URIs. @makzimus could you set the 'dotnet.server.trace' setting to 'Trace' and attach the contents of the C# LSP trace logs? That should tell us what URI its throwing on. Thanks! |
Log file snippet: |
Thanks, I think the logs have enough info to fix. I'll take a look. |
Taking a look at them one by one (minus the query parameters): Splitting it up into parts (using this ref) we have The authority is defined as Taking a look at
Which '#' (what |
Not sure there is much we can do here at the moment. For the first URI we need dotnet/runtime#64707, for the second I think you'd need to reach out to whichever extension is creating these URIs as I don't think it's valid. |
A better behaviour might be to not use |
Getting the same, dozens of errors when scrolling a document |
I am experiencing this issue - using the GitLens extension - while scrolling in Diff view. I understand the comments above about the fix being required elsewhere, but please could you consider not alerting so many errors? It makes reviewing diffs very annoying! Thanks. |
At this point I don't care when the bugs get fixed I just want to be able to hide the error message from popping up. @davidwengier any insight on this? |
This has nothing to do with me, but personally speaking I also think the toasts for every failed LSP request are annoying and wish they could be turned off or just didn't happen. I don't even know if that is possible though. I also agree with @dibarbet that if an extension is not sending valid URIs they should fix that. LSP is a pretty objectively URI based protocol. |
So two things -
Could you file a separate issue on dotnet/razor? Second thing is that for the original issue here, its actually not the extension that is creating the pop-up boxes. We error the request (because we don't know the URI), but then vscode's LSP client is the one actually creating the pop-up. I do not know of a way to prevent that, other than not erroring the request. But I'll leave this open so we can take a look. |
Created an issue for the second point above here: #6977 |
The latest prerelease of the C# extension should fix the issue where normal git diff windows throw errors (related to #6973). I suspect the perforce diffs may still throw errors due to the issues with the URIs they are creating (see above). That likely needs a fix on their end. Closing this issue. If you're still seeing these errors (outside of the perforce diff), please file a new issue. |
Type: Bug
Issue Description
When diffing a csharp file the extension will continuously spam 2 errors while scrolling:
Request textDocument/inlayHint failed
Request textDocument/semanticTokens/range failed.
Steps to Reproduce
Expected Behavior
No errors.
Actual Behavior
Errors appear.
Logs
C# log
Environment information
VSCode version: 1.81.1
C# Extension: 2.0.416
Using OmniSharp: false
Visual Studio Code Extensions
Extension version: 2.0.416
VS Code version: Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:22:42.175Z)
OS version: Windows_NT x64 10.0.22621
Modes:
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
A/B Experiments
The text was updated successfully, but these errors were encountered: