-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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: returning old versions when the proxy knows of a newer version #46369
Comments
Note the presence of a later commit doesn't necessarily mean it is on the default branch which is what latest maps to |
In this case the later commit does live on the default branch. If I get the default branch explicitly it gets the later commit, but then if I get latest again, it downgrades again.
If this is behaving as intended, the behavior is surprising and not intuitive. |
Note that the later commit is 35 minutes old but is still not being picked up by latest. According to https://proxy.golang.org:
|
Thanks for filing the issue. At this point, it looks like the So this particular issue has resolved itself. However, we can take a look at our logs to determine whether something went wrong on our end. I was able to confirm that we had fetched it within ~5 minutes of the commit: it was committed at |
To follow-up, I want to expand the FAQ entry you linked:
If someone wants a particular commit to show up very quickly in the I still don't have an explanation for why it took >35 minutes, since that shouldn't happen, even for a pseudoversion. But please let us know if that happens again and provide as many timestamps as possible so we can debug on our end. Thanks! |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes, occurs on Go 1.16.4 too.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
The latest version of the tool is
v0.0.0-20210525162741-cfbe68afa074
.The old version of the tool is
v0.0.0-20210525064236-6b157d2a519a
.What did you expect to see?
I expected that the proxy.golang.org Go proxy would return the latest commit for a tool once it knew of the latest commit of the tool.
I expected that using the defaults for GOPROXY, which prefers proxy.golang.org, would be more convenient than customizing the GOPROXY.
What did you see instead?
The proxy.golang.org Go proxy returning an old version of the tool, even after it has successfully delivered the latest version of the tool.
The text was updated successfully, but these errors were encountered: