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

sum.golang.org: repeated 500 internal server errors when fetching very new versions #70042

Open
mvdan opened this issue Oct 25, 2024 · 4 comments
Assignees
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. proxy.golang.org Tools This label describes issues relating to any tools in the x/tools repository.

Comments

@mvdan
Copy link
Member

mvdan commented Oct 25, 2024

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.

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.

@cagedmantis cagedmantis added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Oct 28, 2024
@cagedmantis cagedmantis added this to the Unreleased milestone Oct 28, 2024
@cagedmantis
Copy link
Contributor

cc @golang/tools-team

@cagedmantis cagedmantis added the Tools This label describes issues relating to any tools in the x/tools repository. label Oct 28, 2024
@ansaba
Copy link

ansaba commented Nov 5, 2024

cc: @samthanawalla

@samthanawalla
Copy link
Contributor

I'll look into this more after the freeze but it makes sense to return 404 instead of 500.

I suspect it is due to timing out while waiting for the fetch to finish so we should return 404 early in that case and not wait.

@samthanawalla samthanawalla self-assigned this Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. proxy.golang.org Tools This label describes issues relating to any tools in the x/tools repository.
Projects
None yet
Development

No branches or pull requests

7 participants