-
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: panics on master when attempting to jump to a definition in a module not in a loaded workspace #37045
Comments
I'm getting this as well. Notably, if you then restart |
Change https://golang.org/cl/218322 mentions this issue: |
Thanks for reporting this! This is caused by the fact that we only set the parse mode to "full" for packages in the workspace (forgetting to account for opened files). I will have a fix for this shortly. |
Change https://golang.org/cl/218499 mentions this issue: |
Add regression tests for GoToDefinition. In particular, exercise the panic from golang/go#37045. Updates golang/go#37045 Updates golang/go#36879 Change-Id: I67b562acd293f47907de0435c14b62c1a22cf2ee Reviewed-on: https://go-review.googlesource.com/c/tools/+/218322 Run-TryBot: Robert Findley <rfindley@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Rebecca Stambler <rstambler@golang.org>
Please answer these questions before submitting your issue. Thanks!
What did you do?
attempting to follow a definition to a function in a module not in a loaded workspace
What did you expect to see?
either for it to work, or not to work (maybe with an info message if not working)
What did you see instead?
gopl crashes. I have enabled -rpc.trace.
the immediate error is
2020/02/05 14:25:03 io: read/write on closed pipe
example 1
example 2
Build info
Go info
The text was updated successfully, but these errors were encountered: