-
Notifications
You must be signed in to change notification settings - Fork 18.1k
proxy.golang.org: unexpected status 410 Gone #32461
New issue
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
Comments
/cc @katiehockman |
Where did that pseudoversion come from? 65db074680f5 in that repository is tagged as v12.2.0, so it's questionable to use a pseudoversion to refer to it. I'm not sure offhand why the mirror is rejecting the request though. |
In case this can help: $ cat go.mod | grep vegeta
github.com/tsenart/vegeta v12.1.1-0.20190104112155-65db074680f5+incompatible
$ cat go.sum | grep vegeta
github.com/tsenart/vegeta v12.1.1-0.20190104112155-65db074680f5+incompatible h1:BOkXQRcpd/1H9QU5eLMWY6Swb+2oA6KldbQWdKT9zHY=
github.com/tsenart/vegeta v12.1.1-0.20190104112155-65db074680f5+incompatible/go.mod h1:Smz/ZWfhKRcyDDChZkG3CyTHdj87lHzio/HOCkbndXM= |
That pseudo-version would be an appropriate name for the commit if the tag was not added until some later point. (This is one of the cases described in #27173 (comment), in which we need to accept a pseudo-version below what is implied by the current tags.) |
For (my) reference, a good thing to try in the future for issues similar to this one is to run the same command with In this case, it seems the problem only happens with GOPROXY set to mirror and not direct:
|
We've released a change that improves this behavior; the query that previously returned an error will now return |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What did you do?
Use go index:
What did you expect to see?
Should download modules.
What did you see instead?
The text was updated successfully, but these errors were encountered: