You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The auto-detection is not perfect. Probably it should print what it chose, so that if it's wrong maybe you avoid a debugging session. You can always write the module line yourself.
rsc
changed the title
x/vgo: vgo build with empty go.mod file picked up the wrong module root
x/vgo: print auto-detected module line during go.mod init
Apr 2, 2018
rsc
changed the title
x/vgo: print auto-detected module line during go.mod init
x/vgo: print auto-guessed module setting during go.mod init
Apr 2, 2018
rsc
added
the
NeedsFix
The path to resolution is known, but the work has not been done.
label
Apr 2, 2018
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go 1.10
Does this issue reproduce with the latest release?
n/a
What operating system and processor architecture are you using (
go env
)?darwin/amd64
What did you do?
I'm trying vgo on heptio/contour, a moderate project which depends on the kubernetes client-go library. My $GOPATH is set to $HOME
What did you expect to see?
What did you see instead?
This may be because I have renamed my origin branch to be my fork of contour
The text was updated successfully, but these errors were encountered: