gitpod-io
Goland does not set GOPATH to the same value as Workspace environment variables
Bug description
When I launch gitpod on one of my personal repositories, Goland automatically detects GOPATH (in IDE config) and sets it to home/gitpod/go.
If I do the exact same thing with our gitpod-io/gitpod repo, it for some reason sets it to home/gitpod/go-packages. This then causes the IDE to not have the dependencies and requires me to manually ask it to fetch and index the dependencies.
Steps to reproduce
Launch Goland on gitpod-io/gitpod repository and observe the GOPATH variable in Goland Settings is set to home/gitpod/go-packages
Screenshot of the GoLand Preferences (right after the workspace startup) with "Use GOPATH that is defined in system environment" set:
And then, here is what it looks like when we uncheck this option:
Workspace affected
No response
Expected behavior
No response
Example repository
No response
Anything else?
As a possible datapoint, if I add GOPATH=/workspace/go into my Gitpod env variables, it then shows up in the IDE configuration. However, that should not be needed, as the GOPATH in the workspace image is set to /workspace/go already.
See internal thread
Extra info: When we uncheck the "Use GOPATH that is defined in system environment" option and ask GoLand to sync the project dependencies, it prints this warning:
GOROOT=/home/gitpod/go #gosetup
GOPATH=/home/gitpod/go #gosetup
/home/gitpod/go/bin/go mod tidy #gosetup
warning: GOPATH set to GOROOT (/home/gitpod/go) has no effect
On YouTrack, when searching for Goland sync dependencies or GOPATH, I could only find these related issues:
-
Implement ability to automatically run
go mod download - Ask users to download missing dependencies when a project is created from existing sources
- Go Modules dependencies are not synchronized
We're closing this issue, as the GOPATH in GoLand settings is now correctly set with the same value from the workspace's GOPATH environment variable.
