-
Notifications
You must be signed in to change notification settings - Fork 18k
x/tools/gopls: fail gracefully without a Go installation #41701
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
Thanks for this report! Do you mind sharing the output of the |
As a note to the person who fixes this -- we currently print |
@stamblerre, your requested information - output of
VS Code Settings:
|
@jherman It looks like This looks like a new problem triggered by VS Code Go 0.17.1 which no longer mutates While we are fixing the issues in gopls and the extension, you can try one of the followings
I recommend option 3, but not sure what's the easiest way to configure PATH env vars on windows. |
@hyangah Options 3 fixed the issue. Thank you. |
Change https://golang.org/cl/258312 mentions this issue: |
I'm on Ubuntu. |
Change https://golang.org/cl/258517 mentions this issue: |
…ce the view is created Printing the Go version without the session's go command runner means that we may not find the right Go version. Also, panicking when we cannot find a go command is not useful to the user--show the error as a view initialization error instead. Fixes golang/go#41701 Change-Id: I0e0753da9795b1c78331db1faecd27c2bfcee9b4 Reviewed-on: https://go-review.googlesource.com/c/tools/+/258312 Trust: Rebecca Stambler <rstambler@golang.org> Run-TryBot: Rebecca Stambler <rstambler@golang.org> gopls-CI: kokoro <noreply+kokoro@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Robert Findley <rfindley@google.com> (cherry picked from commit 66e72d0) Reviewed-on: https://go-review.googlesource.com/c/tools/+/258517
gopls version: v0.5.0
gopls flags:
ATTENTION: PLEASE PROVIDE THE DETAILS REQUESTED BELOW.
Describe what you observed.
The text was updated successfully, but these errors were encountered: