Do you have experimentalWorkspaceModule enabled, or any other unusual flags set in your settings? Please follow the instructions at https://github.com/golang/vscode-go/blob/master/docs/troubleshooting.md#collect-gopls-information for VS Code to generate a log file and collect settings.

A repro would also be helpful. If you're working on github.com/openshift/ci-tools, I tried opening that project and it seemed to go fine with default gopls settings.

@heschik doesn't happen on master, but here: openshift/ci-tools@c50dc4e

I don't have any special settings. I do not use vscode but vim-go/coc.nvim:

$ ps xf|rg gopls|rg -v rg
3392140 ?        Sl     0:00  |       |   \_ gopls -remote=auto -logfile=auto -debug=:0 -remote.debug=:0 -rpc.trace
3392085 ?        Ssl    0:00  |       \_ /home/alvaro/git/golang/bin/gopls -remote=auto -logfile=auto -debug=:0 -remote.debug=:0 -rpc.trace
3392126 ?        Ssl    0:21  |           \_ /home/alvaro/git/golang/bin/gopls serve -listen unix;/run/user/1000/gopls-d12775-daemon.alvaro -listen.timeout 1m0s -debug :

Logs:

• https://gist.github.com/alvaroaleman/1ee58138c983155377737ec2d8aa4d6a
• https://gist.github.com/alvaroaleman/32b224edd095176acff0843ab5885cf2

The error are in the second log towards the end go/packages.Load: err: exit status 1: stderr: go:[...]

Thanks for the logs. It appears that when you jumped to definition on a type in the vault module, your editor added that folder as a workspace root:

[Trace - 17:58:55.290 PM] Received response 'textDocument/definition - (3)' in 480ms.
Result: [{"uri":"file:///home/alvaro/git/golang/src/github.com/openshift/ci-tools/vendor/github.com/hashicorp/vault/api/sys_auth.go","range":{"start":{"line":76,"character":5},"end":{"line":76,"character":22}}}]


[Trace - 17:58:55.336 PM] Sending notification 'workspace/didChangeWorkspaceFolders'.
Params: {"event":{"added":[{"uri":"file:///home/alvaro/git/golang/src/github.com/openshift/ci-tools/vendor/github.com/hashicorp/vault/api","name":"/home/alvaro/git/golang/src/github.com/openshift/ci-tools/vendor/github.com/hashicorp/vault/api"}],"removed":[]}}

At that point I think gopls is working as intended, though I could be wrong. I don't know enough about vim to tell you how to avoid this behavior. @findleyr might.

It appears this is vim-go. I didn't intend to use the vim-go lsp integration in the first place, I only have it for the highlighting and coc-nvim for the lsp integration. The latter doesn't have any issues with this.

Thanks a lot for your help!