Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upcmd/go: print useful reason when 'go mod tidy' and 'go get' fail due to missing git authentication credentials #31353
Labels
Milestone
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
• If user was authenticated to pull from cloud.google.com:
The requested module to be downloaded and defined in go.mod. No problem.
• If user was not authenticated to pull from cloud.google.com:
This
go get
output needs to convey an actionable error reason for the user to fix the situation. Something like:What did you see instead?
This
go get
output does not convey any actionable error reason for the user to fix the situation.I had to dig deeper with
go get -v -x
to find the command that failed. Thanks @thepudds and @heschik.Then I had to manually execute the failing command (
git ls-remote -q ...
) to find the actual/useful failure reason.go get -v -x "google.golang.org/grpc"
Output