-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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/gopls: file changes not reflected in results #35526
Comments
Thank you for filing a gopls issue! Please take a look at the Troubleshooting guide, and make sure that you have provided all of the relevant information here. |
Has this happened to you more than once or was it just in this instance? If it happens often, can you share a |
It happens often(nearly every time), and not only to me. $ gopls.exe version golang.org/x/tools/gopls 0.2.0 golang.org/x/tools/gopls@v0.2.0 h1:ddCHfScTYOG6auAcEKXCFN5iSeKSAnYcPv+7zVJBd+U= some
|
Can you please share the full |
Here is the full |
Based on your logs, it looks like This might also be related to #35584. |
Closing this issue as it's now almost 2 months old. @leerayven: Please open a new issue if you are still encountering problems. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I was using vscode-go together with gopls and other go tools (all installed automatically), when I made some changes to the file inside the vscode editor, such as adding or deleting some lines, linting or auto-completion couldn't work correctly. I had to reload the window to get things right.

In the above example, when my mouse cursor stops above "splitDhash", it came out the description of "blockMasks" just because I inserted an empty line at line 122.
What did you expect to see?
Changes inside the vscode editor should be tracked.
What did you see instead?
Changes inside the vscode editor are not tracked.
The text was updated successfully, but these errors were encountered: