-
Notifications
You must be signed in to change notification settings - Fork 669
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
Real Time Compile and Error reporting not working #2578
Comments
From @motor75 on October 2, 2018 16:35 Additional details - in the Problems window, I can see the errors and when I double click on them, it opens the same file in a new editor tab (now the same file is opened twice) and shows the red underline under the code in question. |
@motor75 In the Problems panel, what's listed as the source of the errors? The csharp extension? |
From @motor75 on October 2, 2018 17:29 @RMacfarlane - I restarted VS Code and all is working now...but eventually this will start happening again and I'll let you know....but when it was happening earlier (from my previous post), it showed the same file as the source separately - as if it was seeing two copies of it when only one exists. Very strange. I thought maybe I have some circular logic in the solution file or in my unit test project file - but this is not the case. I have two projects; the solution has each of them only once and the unit test project references the web api project only once. |
From @motor75 on October 4, 2018 15:30 @RMacfarlane - it took a day but I'm back to nothing showing compile errors. See attached screen shot... Here's my Problems window....no problems showing... Also it seems debugging via XUnit no longer works in this state... There is this error in the Log window which is most likely the reason that this is occurring...and I see a bunch of these in the last 3 or 4 minutes in the same window (they're all the same error repeated over and over): [2018-10-04 11:27:12.412] [renderer1] [error] Pending request cancelled: /codecheck: Error: Pending request cancelled: /codecheck |
From @motor75 on October 4, 2018 15:34 It appears that this all started with this error (which is different from what I put in my previous post): [2018-10-04 11:19:06.920] [renderer1] [error] This socket is closed: Error: This socket is closed |
@motor75 Could you post the output from your OmniSharp log(View--> Output--> OmniSharp log) |
@akshita31 I have come across this issue again...except now it is causing XUnit to fail (I can't debug or run any tests). Below is the output from the Log(Window) and also from the OmniSharp Log that you requested. Also, I'm seeing this error in the log... OmniSharp Log: Log(Window): |
@motor75 It seems that the OmniSharp process is crashing for some reason, due to which you are losing the intellisense. We have seen this issue in Mac/Linux , but this is the first time the error reproduces on Windows. Can you provide a minimum repro project that would help us debug the issue. Also can you set, Omnisharp.logginglevel--> Debug and then "Restart OmniSharp" and then paste the output from omnisharp log when the crash happens. |
@akshita31 The projects that I'm working on contains confidential information that I would not be able to share. However, I have set the logging level to debug and will post the Omnisharp logs when the issue reoccurs. Thanks! |
@akshita31 The error has reproduced itself. I have attached the log file - if you open it up, near the top the issue starts at line 316 (around 16:28 10-19-2018). Below I pasted what's showing in the OmniSharp log (as you can see, there's no errors). Just FYI - this is happening on the 3 projects/solutions that I work on - so I don't think this is a problem with the projects. Starting OmniSharp server at 10/19/2018, 3:01:32 PM OmniSharp server started. Starting OmniSharp on Windows 6.2.9200.0 (x64) |
@motor75 Did you set omnisharp.loggingLevel --> Debug ? |
I had only the user setting set to debug; workspace was set to informational. I set both to debug as I assume that the workspace setting overrode the user setting (although that isn't entirely clear on the settings U/I). |
@akshita31 The issue has come up again - I attached the log (Window) output and the Omnisharp Log output. Let me know if you need anything further from me. Thanks! |
@motor75 Are you working with the latest version of the extension ? |
@akshita31 - I am on 1.17.1. This appears to be the latest, no? |
@akshita31 - I'm back to getting errors in the logs with real time compiling and error reporting not working. I get no intellisence either. I completely uninstalled Omnisharp, deleted the extensions directories in my .vscode folder under my user and reinstalled the extension but that did nothing to change the issue. Attached is the error log. Any thoughts as this is getting to make this extension not usable. |
@motor75 Do you have an OmniSharp log. Please post the output from that and sorry I couldnt keep track of this one |
@akshita31 I only have what I provided above unless you can point me somewhere on my HDD where the log is located. |
From @motor75 on October 2, 2018 16:22
Issue Type: Bug
It seems that since I have introduced solution files (.sln) into my projects, the red squiggles that show errors as you're coding has stopped altogether. I have multiple projects in which this is occurring. It had been working, but seems to have stopped since I put existing projects in solutions. I had created an ASP.NET Core Web API project and wanted to add a Unit Test project to it - thus the need for a solution file. However, that seems to be when this issue started. I have not yet tried uninstalling and reinstalling Visual Studio Code because I wanted to report the issue and have it be replicated so that a fix can be made.
VS Code version: Code 1.27.2 (f46c4c469d6e6d8c46f268d1553c5dc4b475840f, 2018-09-12T16:17:45.060Z)
OS version: Windows_NT x64 10.0.15063
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: disabled_off
native_gpu_memory_buffers: disabled_software
rasterization: unavailable_software
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
Extensions (2)
Copied from original issue: microsoft/vscode#59836
The text was updated successfully, but these errors were encountered: