-
Notifications
You must be signed in to change notification settings - Fork 18k
x/tools/cmd/gopls: non .go files cause gopls log errors #32178
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
Comments
I'm having a hard time reproducing this. Can you give the contents of the Go file and the go.mod file? Did you trigger the completion from inside the |
No, the completion is triggered within the
The error messages start coming back after I've opened the
Regarding the contents of the files, they're in the log above - or did I misunderstand? |
Sorry, I had a difficult time finding them in the log - it's usually easier for me to repro something just based on file contents. I was able to reproduce the error though. |
Change https://golang.org/cl/178679 mentions this issue: |
Now that golang/go#32178 is fixed we can start to watch changes to go.mod files and communicate those in the same way that changes to .go files outside of the editor are.
Now that golang/go#32178 is fixed we can start to watch changes to go.mod files and communicate those in the same way that changes to .go files outside of the editor are.
Now that golang/go#32178 is fixed we can start to watch changes to go.mod files and communicate those in the same way that changes to .go files outside of the editor are.
Now that golang/go#32178 is fixed we can start to watch changes to go.mod files and communicate those in the same way that changes to .go files outside of the editor are.
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?
The following log shows interaction with
gopls
for a completion request. But as part of that we also open ago.mod
:Log Output
The opening of the
go.mod
causes the error lines:and
If the
go.mod
is not opened, these error messages are not reported.What did you expect to see?
No error messages for the
go.mod
file.What did you see instead?
The above error messages
cc @stamblerre @ianthehat
The text was updated successfully, but these errors were encountered: