x/tools/gopls: multi-modules workspace fails with v2+ private module #41807
Labels
FrozenDueToAge
gopls
Issues related to the Go language server, gopls.
Tools
This label describes issues relating to any tools in the x/tools repository.
Milestone
What version of Go are you using (
go version
)?What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I'm using vscode and I've enabled the multi-modules workspace experimental option.
My configuration:
I've opened with vscode a directory containing all my private (Github projects).
Some of these projects are "v1" and some of them are "v2+".
The
go.mod
of my "v2+" projects are properly configured, and themodule
correctly shows the same major version.They are "normal" small projects, not a monorepo.
I've configured my global
~/.gitconfig
with:(it was working fine previously anyway)
What did you expect to see?
gopls
should work.What did you see instead?
gopls
fails to initialize, and prints this message:It fails in 2 cases:
Removing all "faulty" projects fixes the issue.
It was working fine with the previous workflow:
But this previous workflow is consuming a lot of RAM (gopls).
So it's not sustainable on the long term.
The more projects I had, the more memory it uses.
I've got ~70 projects, and I need to open them all.
With the new multi-modules workspace, my memory usage is decreased by 10x ! 👍
The text was updated successfully, but these errors were encountered: