proxy.golang.org: "invalid version" reported for valid commit pulled through the proxy #53906
Labels
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
proxy.golang.org
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
When a new commit is submitted to the tip of CUE, the following CI step runs:
i.e. we intentionally pull that commit through the proxy. Occasionally, this gives output similar to:
This happened twice today (times in parentheses):
This error also happens as part of another CI workflow, where we try to
go get
the default branch (master
) through the proxy.Per an exchange with @bcmills on Slack, I'm creating this issue to track how often this occurs.
A retry is almost always sufficient to "fix" this failure, but when this happens as part of CI, the retry is significantly more involved.
What did you expect to see?
No errors. The commit is definitely there, and in the case of the default branch, that's never not been there.
What did you see instead?
As above.
Please let me know if there are any specific details that would help in tracking down the cause.
cc @mvdan
The text was updated successfully, but these errors were encountered: