Description
We have had four CI jobs fail in the past week due to sum.golang.org reporting 500 internal server errors as well as an unexpected EOF.
- https://github.com/cue-lang/cuelang.org/actions/runs/11405713492/job/31737794702
- https://github.com/cue-lang/cuelang.org/actions/runs/11406304337/job/31739760236
- https://github.com/cue-lang/cuelang.org/actions/runs/11494340883/job/31991655336
- https://github.com/cue-lang/cuelang.org/actions/runs/11514929154/job/32054554147
The two types of errors we have seen look like:
go: cuelang.org/go@v0.11.0-alpha.3.0.20241018144220-537f744a9cc7: verifying go.mod: cuelang.org/go@v0.11.0-alpha.3.0.20241018144220-537f744a9cc7/go.mod: reading https://sum.golang.org/lookup/cuelang.org/go@v0.11.0-alpha.3.0.20241018144220-537f744a9cc7: 500 Internal Server Error
go: cuelang.org/go@v0.10.1: verifying module: cuelang.org/go@v0.10.1: Get "https://sum.golang.org/lookup/cuelang.org/go@v0.10.1": EOF
These CI jobs are doing what is effectively:
go mod init
go get cuelang.org/go@${commitRef}
where ${commitRef} is a commit hash which was just pushed to master.
We are aware that proxy.golang.org and sum.golang.org may respond with status codes like 404 for the first fifteen to thirty minutes as they discover the new version (#49916 (comment)), but I still assume that the 500 and EOF errors are unexpected and should be fixed.
Moreover, we do dozens of these runs per week, and only very few fail, so sum.golang.org often answers these requests correctly without any issue.