gopls warn that it cannot read env variables GOROOT, GOPATH, GOMODCACHE

[fedxyz]

Hi,

when using the neovim snap packages (ubuntu) and lsp when starting nvim gopls give me messages like this one

[gopls] identify GOROOT dir cmd failed with code 0: { "go", "env", "GOROOT" }

same message for GOPATH and GOMODCACHE. and I have to confirm these messages on start and every time I open a new (go) file.

Using neovim from a classic installation (same version) works with no warnings.

go is installed via snap package too, gopls is installed in go dir in my home /home/myuser/go/bin/gopls.

Thanks for the help.

[justinmk]

Why do you think this has anything to do with Neovim, as opposed to a general issue about snap?

[fedxyz]

I'm not sure how snap sandboxing works exactly, but I reported it here because the issue only happens with neovim-snap. The same Neovim version installed normally works fine with no warnings. If this should be reported somewhere else, let me know.

[justinmk]

only happens with neovim-snap

As in, you tried other snap apps and confirmed it doesn't happen in other snap apps? The env vars are visible in those snap apps?

Comparing to non-snap Neovim does not tell us much.

[fedxyz]

I haven't tested other snap apps because I don't use any that would need these specific Go env vars. I do use other snaps (Firefox, Chrome, IntelliJ) but I have no way to tell if they read env variables the same way gopls does. This is a specific nvim+LSP+Go setup that I can't reproduce elsewhere.

I reported it here because I'm using neovim-snap and non-snap Neovim works fine. Where else would you suggest reporting an issue like this?

[justinmk]

go is installed via snap package too, gopls is installed in go dir in my home /home/myuser/go/bin/gopls.

Does which go and which gopls show the correct paths when run from :terminal in the snap Nvim? And do those commands work from :terminal ?

It might be related to snap "sandboxing".

I reported it here because I'm using neovim-snap and non-snap Neovim works fine. Where else would you suggest reporting an issue like this?

This is likely a behavior related to snap in general, so start with their docs. I don't know much about snap.

[fedxyz]

in :terminal which go and which gopls works

I've tested it: :!go env GOROOT (GOPATH and GOMODCACHE too) works in standard Neovim but returns nothing in neovim-snap.
If this is an unfixable snap limitation, then the snap package doesn't provide equivalent functionality to standard Neovim for LSP usage, which imho seems like a significant problem.

Edit:
:terminal go env GOROOT/GOPATH/GOMODCACHE works

[justinmk]

snap package doesn't provide equivalent functionality to standard Neovim for LSP usage, which imho seems like a significant problem.

Indeed. We are open to concrete improvements to the snap build, if possible, but it may not be fully fixable because of Snap design. Nothing we can do about that.