/ go Public
x/tools/gopls: consider to turn off
buildvcs inside gopls
Issues related to metadata loading in gopls
Issues related to the Go language server, gopls.
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
This label describes issues relating to any tools in the x/tools repository.
compiled with go1.18 (google-golang)
What did you do?
We have a project that has a third-party go project as its git submodule.
go.work has only
I opened vscode from
my_project, so gopls sees
my_projectas the workspace root.
What did you expect to see?
What did you see instead?
All go files in the their_project directory get errors with source
I understand this is an error message from
go, and I can work around by disabling the
However, what's puzzling is, if I run
their_project, it runs without an error.
I don't know what's right default behavior for the go command (this is probably a niche use case) cc @bcmills
but these confusing error messages make me think
goplsdisable vcs build stamping by default when running go commands.
(why does gopls have to care about build stamping?)
The text was updated successfully, but these errors were encountered: