We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The golang.org/x/mod package/dependency triggers Git "invalid version" error.
Add "require gocloud.dev v0.20.0" to go.mod which yields the following error when trying to build code:
go.mod
go: found gocloud.dev/blob in gocloud.dev v0.20.0 go: [email protected] requires cloud.google.com/[email protected] requires cloud.google.com/go/[email protected] requires golang.org/x/[email protected] requires golang.org/x/[email protected]: invalid version: git fetch --unshallow -f origin in /home/centos/go/pkg/mod/cache/vcs/13df7481b5cc3358460b717a6142fe8dbaae7652e5d05689849f419ffd40ac12: exit status 128: fatal: git fetch-pack: expected shallow list
Steps to reproduce the behavior.
A clear and concise description of what you expected to happen.
v0.20.0
If I downgrade to v0.19.0 the problem goes away.
n/a
The text was updated successfully, but these errors were encountered:
This looks like it might be related to golang/go#38373, can you take a look? Which OS and go and git versions are you using?
go
git
Sorry, something went wrong.
I will check the version of Git, shortly. I am using Go 1.14.4.
No branches or pull requests
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
The golang.org/x/mod package/dependency triggers Git "invalid version" error.
To Reproduce
Add "require gocloud.dev v0.20.0" to
go.mod
which yields the following error when trying to build code:Steps to reproduce the behavior.
Expected behavior
A clear and concise description of what you expected to happen.
Version
v0.20.0
If I downgrade to v0.19.0 the problem goes away.
Additional context
n/a
The text was updated successfully, but these errors were encountered: