-
Notifications
You must be signed in to change notification settings - Fork 17.6k
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
x/tools/cmd/gopls: wrong error messages after gopls restart inside of editor (by means of editor) #32909
Comments
This sounds like your VSCode-Go issue: microsoft/vscode-go#2633. I will close this issue in favor of that one. |
It's clear that these issues are different. In the mentioned case there is even no |
My apologies, I assumed that the error was related to one of the other issues you had filed. |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
Nice. |
FWIW I haven't gotten this error in the past couple days. I've been keeping up to date with the latest gopls so maybe it got fixed there somewhere @inliquid what version/commit of gopls are you using? |
I think it depends on how you restart gopls, if you use the Restart Language Server thing, it does not seem to clear out existing diagnostics, and of course the new instance of gopls knows nothing about the diagnostics that were already sent so it cannot clear them. |
Usually (if no errors, etc) "Restart Language Server" works. This is quite rare error and I didn't see it since quite a while. |
@jguenther I always use latest master version. Updating it regularly. |
VS Code. After some editing I came to some strange error, and decided to restart
gopls
by means of editor But the thing is that after restart (no any other actions taken) there are false errors, see log below. This situation repeated each time restart feature was used (tried several times). However when I restarted whole editor, it disappeared.The text was updated successfully, but these errors were encountered: