-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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: go list error opening Go source tree #35847
Comments
I'm not able to reproduce this on master. Is this still an issue for you? |
I tried again and hit #36587... |
OK that was a me problem. Works for me. @myitcv, wanna take another look? |
I'm still seeing an error being logged as of 473961e:
|
Could that error be related to your Go installation? Does running |
This might be https://golang.org/issue/36188. Are you absolutely sure that gopls is using the |
Note I'm loading this file from the root of
gives not output. @heschik
Possibly.
100% sure. It's even logged as such. |
Note
As a result I don't think this is a |
I think that would be the problem. The |
Oh wow. Quite honestly I hadn't even spotted there was a Perhaps a point worth highlighting to folks who work on the Go source tree and use Either way, there is no bug per say here so I'll close this. Thanks for your responses and sorry for the noise. |
What version of Go are you using (
go version
)?Note that
github.com/myitcvforks/tools v0.0.0-20191119111301-0222b4b716c6
andgithub.com/myitcvforks/tools/gopls v0.0.0-20191119111301-0222b4b716c6
correspond to thex/tools
95cb2a1 with 80313e1 cherry picked on top. Reason being, we can't move beyond 95cb2a1 because otherwise we start tripping over the mistmatched versions problem described in #35114Does 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?
Opened Vim +
govim
in the root of a clone of the Go source tree:Got the following error message from
gopls
:What did you expect to see?
No error
What did you see instead?
As above.
gopls
log as follows: fail.logcc @stamblerre
The text was updated successfully, but these errors were encountered: