confusing message about multi-root setup #1848
Labels
Milestone
Comments
|
Can you please Run Ctrl+Shift+P (Cmd+Shift+P on Mac OS) > Go: Locate Configured Go Tools command, and share the output? |
|
@hyangah I tried that, the "Output" area in vcode filled with 1500+ lines of output. I kept the first part: I removed the ever-repeating listing of variables for each workspace folder to keep it brief here. If you're looking for something specific, just let me know. |
|
Change https://golang.org/cl/356909 mentions this issue: |
gopherbot
pushed a commit
that referenced
this issue
Oct 19, 2021
Updates #1848 Change-Id: I482625276bd4dd8adefea90c0ae595c77abae48c Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/356909 Trust: Rebecca Stambler <rstambler@golang.org> Run-TryBot: Rebecca Stambler <rstambler@golang.org> Reviewed-by: Suzy Mueller <suzmue@golang.org>
|
@MartinEmrich Could you please share your complete logs? It would be helpful to see how these variables differ between your workspace folders. If you do not want to attach your complete logs, could you please include the following for each workspaceFolder? Thanks! |
|
The lower workspace part was huge (Its over 20 folders), so I removed duplicates: So no variables differ from each folder. I guess they are default values provided by vscode, as there is not a single Golang project in my workspace. |
|
@MartinEmrich the latest version of vscode-go includes some helpful error message for debugging. Do you see any? |
|
@hyangah Thanks! after reinstalling the go extension, indeed the new version did put all assumed gopaths into the error message (sadly without the source of the gopath). And actually there is some Go code in my workspace, so the extension activating itself was no error. And after all, I intended to start a new go based project, which triggered the issue for me in the first place... Finally, in the meantime I learned that "multi-root setup" is not a Golang concept, but rather a vscode concept, so now I understand what could be going on here. So for me, the mystery is solved, the issue can be closed if necessary. |
|
@MartinEmrich glad the mystery is solved, and thanks for following up! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What version of Go, VS Code & VS Code Go extension are you using?
Version Information
go versionto get version of Go from the VS Code integrated terminal.gopls -v versionto get version of Gopls from the VS Code integrated terminal.code -vorcode-insiders -vto get version of VS Code or VS Code Insiders.Go: Locate Configured Go Toolscommand.Working on Windows with WSL remote in Debian 11 WSL2 environment.
Share the Go related settings you have added/edited
None, the message occured right after installing the vscode go extension.
Describe the bug
After installing the Go language extension, I get this message pop-up:
I have not set any "GOPATHs", I do not know what a "multi-root set-up" is in "Go speak". The messages gives me no clue on what to do next.
Steps to reproduce the behavior:
I assume this does not happen for everyone (or it would have been reported long ago), so a characteristic of my very workspace setup (many folders with different types of projects, repositories) might trigger this? But the message gives no hint on what to do to fix it.
The text was updated successfully, but these errors were encountered: