-
Notifications
You must be signed in to change notification settings - Fork 14
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
[BUG] Project system ran into an unexpected problem #1470
Comments
I am having the same issue, error happens as soon as I open a project.
|
It might be causing the C#/.NET IntelliSense to not work properly. I have to restart vscode 2-5 times until the IntelliSense works properly. |
Two requests
@tmeschter is there any way the project system side could log the details of the inner |
C# log:
I'm not sure I can share my solution. But I can tell you it's a solution containing ~46 projects (WebJobs, Functions, Web Apps and a bunch of shared classes) |
@dibarbet - The extension logs contain details about JSON RPC errors. It is hard to say which file is but we have all logs, we can look through it and identify. It would contain which RPC call failed and whole stacktrace and error. @mwkcoding - Please share content of extension logs folder for C# dev kit. You can find extension logs folder using command palette in VS Code. Once you open that you can see a folder with name ending in csdevkit. Content of that folder would be useful. You can send the zip for the folder to @dibarbet via email they provided above if you don't comfortable uploading here. Since this folder contains logs for whole session, please have a fresh session of VS Code to capture the logs when error happens. |
@smitpatel @dibarbet I sent my logs folder zipped to the email provided. |
Thanks got the logs! @smitpatel I'm seeing a few different issues - it would be useful if you could identify what brokered service and process is being called for each. It looks like one of the null refs might be in the project system side? StreamJsonRpc.ConnectionLostExceptionNumerous connection lost exceptions, these are the stack traces I saw
Null referenceI'm also seeing a fair number of null reference exceptions. In one case I see this
the rest I mostly see
|
Everything was (kind of) working for me for a while but this error is popping up once again. Honestly in combination with #722 this is getting rediculous. It's nearly a year now that a microsoft plugin for a microsoft language in a microsoft editor has been close to unusable.
|
Suspecting an issue with Razor projects here. If anyone has a project they can consistently reproduce it in and can share, please email me (dabarbet@microsoft.com). We're working on some changes in parallel that will provide more details on what went wrong when it fails which should be in an upcoming prerelease. |
Using #1410 I was able to get a consistent repro. However I don't think it is the only way to hit this issue.
Note the following exception (requires latest preview 2.51 changes)
It looks like Razor is not returning a C# document - https://github.com/dotnet/roslyn/blob/main/src/LanguageServer/Microsoft.CodeAnalysis.LanguageServer/HostWorkspace/RazorDynamicFileInfoProvider.cs#L74 @phil-allen-msft @ryzngard FYI - we have a number of reports of this issue. |
We are also hitting the issue for the past few weeks.
The JS projects reference a lot of packages and have big
Rolling back the VS Code C# extension to version 2.41.26 or older also fixes the issue. |
Thanks for this information. For the backend, does it include razor/cshtml files or just aspnetcore? If possible can you share a repro? If not possible to share, can you test with the vsix built in https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=833689 ? That will help us know if the targeted fix spans to your scenario as well. Just looking at your information I would guess not, but I very much could be missing something. |
Yes, the backend includes |
Great, Thank you @raurfang! Hopefully we'll have this available in release soon |
The fix should be available in either |
I'm still having this issue even with the new versions. Is there a ticket already tracking this? Making it very difficult to do work in .Net using VSCode, would love to see this resolved :) |
@cklimowski1 would you mind filing a new issue and include the stack you're seeing? We fixed a specific failure but there may be others. |
Describe the Issue
ProjectSystemServerFault_3500c59e-65a9-47b2-8922-9e02834f98f4.failure.txt
Steps To Reproduce
I'm not sure, it comes up every time I open my repo.
Expected Behavior
No notification?
Environment Information
Version: 1.93.1 (system setup)
Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40
Date: 2024-09-11T17:20:05.685Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631
Extension: v1.10.18
The text was updated successfully, but these errors were encountered: