Skip to content
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

proxy.golang.org: unexpected status 410 Gone #32461

Closed
kindermoumoute opened this issue Jun 6, 2019 · 6 comments

Comments

Projects
None yet
5 participants
@kindermoumoute
Copy link

commented Jun 6, 2019

What version of Go are you using (go version)?

$ go version
go version go1.12 darwin/amd64

Does this issue reproduce with the latest release?

Yes

What did you do?

Use go index:

export GOPROXY=https://proxy.golang.org
go mod download

What did you expect to see?

Should download modules.

What did you see instead?

go: github.com/tsenart/vegeta@v12.1.1-0.20190104112155-65db074680f5+incompatible: unexpected status (https://proxy.golang.org/github.com/tsenart/vegeta/@v/v12.1.1-0.20190104112155-65db074680f5+incompatible.info): 410 Gone

@dmitshur dmitshur added this to the Go1.13 milestone Jun 6, 2019

@dmitshur

This comment has been minimized.

Copy link
Member

commented Jun 6, 2019

@heschik

This comment has been minimized.

Copy link
Contributor

commented Jun 6, 2019

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.

@kindermoumoute

This comment has been minimized.

Copy link
Author

commented Jun 6, 2019

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=
@bcmills

This comment has been minimized.

Copy link
Member

commented Jun 6, 2019

Where did that pseudoversion come from? 65db074680f5 in that repository is tagged as v12.2.0

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.)

@bcmills bcmills added the NeedsFix label Jun 6, 2019

@bcmills bcmills modified the milestones: Go1.13, Unreleased Jun 6, 2019

@dmitshur

This comment has been minimized.

Copy link
Member

commented Jun 6, 2019

For (my) reference, a good thing to try in the future for issues similar to this one is to run the same command with export GOPROXY=direct and see if the error happens as well. In that case, the problem is in cmd/go rather than the mirror.

In this case, it seems the problem only happens with GOPROXY set to mirror and not direct:

$ export GOPATH=$(mktemp -d)
$ export GOPROXY=https://proxy.golang.org
$ go mod download -json github.com/tsenart/vegeta@v12.1.1-0.20190104112155-65db074680f5+incompatible
go: finding github.com/tsenart/vegeta v12.1.1-0.20190104112155-65db074680f5+incompatible
{
	"Path": "github.com/tsenart/vegeta",
	"Version": "v12.1.1-0.20190104112155-65db074680f5+incompatible",
	"Error": "unexpected status (https://proxy.golang.org/github.com/tsenart/vegeta/@v/v12.1.1-0.20190104112155-65db074680f5+incompatible.info): 410 Gone"
}
$ echo $?
1

$ export GOPROXY=direct
$ go mod download -json github.com/tsenart/vegeta@v12.1.1-0.20190104112155-65db074680f5+incompatible
go: finding github.com/tsenart/vegeta v12.1.1-0.20190104112155-65db074680f5+incompatible
{
	"Path": "github.com/tsenart/vegeta",
	"Version": "v12.1.1-0.20190104112155-65db074680f5+incompatible",
	"Info": "/var/folders/3m/rg2zm24d1jg40wb48wr0hdjw00jwcj/T/tmp.xbI3lVwp/pkg/mod/cache/download/github.com/tsenart/vegeta/@v/v12.1.1-0.20190104112155-65db074680f5+incompatible.info",
	"GoMod": "/var/folders/3m/rg2zm24d1jg40wb48wr0hdjw00jwcj/T/tmp.xbI3lVwp/pkg/mod/cache/download/github.com/tsenart/vegeta/@v/v12.1.1-0.20190104112155-65db074680f5+incompatible.mod",
	"Zip": "/var/folders/3m/rg2zm24d1jg40wb48wr0hdjw00jwcj/T/tmp.xbI3lVwp/pkg/mod/cache/download/github.com/tsenart/vegeta/@v/v12.1.1-0.20190104112155-65db074680f5+incompatible.zip",
	"Dir": "/var/folders/3m/rg2zm24d1jg40wb48wr0hdjw00jwcj/T/tmp.xbI3lVwp/pkg/mod/github.com/tsenart/vegeta@v12.1.1-0.20190104112155-65db074680f5+incompatible",
	"Sum": "h1:BOkXQRcpd/1H9QU5eLMWY6Swb+2oA6KldbQWdKT9zHY=",
	"GoModSum": "h1:Smz/ZWfhKRcyDDChZkG3CyTHdj87lHzio/HOCkbndXM="
}
$ echo $?
0
@heschik

This comment has been minimized.

Copy link
Contributor

commented Jun 7, 2019

We've released a change that improves this behavior; the query that previously returned an error will now return v12.2.0+incompatible, since that's the more canonical way to reference that commit. If that causes you any trouble please let us know.

@heschik heschik closed this Jun 7, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.