You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ysmood I guess this is fixed now - the sum.golang.org learned about v0.19.2 on 2020-01-28 8:12 EST (8min after this bug was reported)
Based on the log, {proxy,sum}.golang.org tried to fetch that version 7:42:01 EST, and couldn't find the version from the repo (so, "unknown revision v0.19.2"). This result was cached for some time.
I guess the tagging happened around ~7:42 EST based on the github release page, so there must be a race between release(tagging) and that new tag gets accessible by {proxy,sum}.golang.org.
Actually, 7:42:01 EST was the logging timestamp, and the version fetch attempts were made before then. This is clearly because the request to {proxy,sum}.golang.org was sent too early. We will try to find a way to improve the user experience. For now, please make sure if the tagged version is available in the source - one option I can think of is to utilize GOPRIVATE to bypass {proxy,sum}.golang.org first and verify if the version can be fetched from the source.
What did you do?
curl https://sum.golang.org/lookup/github.com/ysmood/kit@v0.19.2
What did you expect to see?
no error
What did you see instead?
The version tag does exist, you can visit
https://github.com/ysmood/kit/tree/v0.19.2
to check it.If you do
curl https://sum.golang.org/lookup/github.com/ysmood/kit@v0.19.1
it will work as expected.Not sure if it's a bug of sum.golang.org or github.
The text was updated successfully, but these errors were encountered: