-
Notifications
You must be signed in to change notification settings - Fork 18k
x/tools/gopls: doesn't work with GOPATH vendoring #36155
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
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. |
I can't reproduce this with gopls master either in GOPATH or module mode. Can you give master a try? |
Yes, I was able to reproduce the issue on master but the logs look much different. |
This particular project is in GOPATH mode using vendored deps. I haven't tried to reproduce the issue in module mode. |
I've also seen a similar issue when creating a new file gopls won't work in that buffer until the file is saved to disk. |
Your logs weirdly don't mention cmp at all, but I was able to reproduce the problem by checking out knative-gcp and following the same steps. Pretty sure this has something to do with vendoring. I get errors like
which are quite suspicious. |
At a bare minimum, this code simply won't work with GOPATH vendoring. |
There's also some code path where we do |
That is probably happening in the Sigh. |
Change https://golang.org/cl/215904 mentions this issue: |
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
)?See logs.
What did you do?
Performed the following steps:
These steps seem to reliably reproduce the issue.
What did you expect to see?
Expected to see completion results for the newly imported package before saving the file.
What did you see instead?
I saw no completion results for cmp.Diff before saving the file but did after saving.
gopls.log
lsp-trace.log
The text was updated successfully, but these errors were encountered: