Hi John, I'm not able to immediately reproduce with VS Code, but if you
file an issue we can investigate.
We'll want the logs with the `-rpc.trace` flag passed to gopls, from a
brief session reproducing the problem.
Thanks,
- Rob
On Thursday, November 7, 2024 at 1:49:44 PM UTC-5 John Robinson
Hi,
Yes, there are some gotchas involved with setting up VS Code with the Go
project. The most common fix is to make sure that the go command resolved
from PATH is the go command built via src/make.bash. There are some more
details
at
https://github.com/golang/tools/blob/master/gopls/doc/adva
You can disable the "composites"
analyzer:
https://github.com/golang/tools/blob/master/gopls/doc/analyzers.md#composites
Update the "analyses" configuration to include "composites": false, as
described here:
https://github.com/golang/tools/blob/master/gopls/doc/settings.md#analyses-mapstringbo
Hi,
Can you follow the instructions
at https://github.com/golang/vscode-go/blob/master/docs/troubleshooting.md
to try to diagnose the problem? It sounds like your workspace is broken
and/or you are having trouble with the language server. Please try
troubleshooting, and if you are unable to ge