We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For example, https://pkg.go.dev/github.com/ipld/go-ipld-prime@v0.10.0 is a 404 and when I request it via the UI, I just get:
Oops! Something went wrong.
Refreshing just gets me back to the start. This version has been published and requested for hours, so it's not a caching thing.
Someone else has been experiencing the exact same issue on Slack with other modules:
https://pkg.go.dev/modernc.org/qbe@v0.0.6
https://pkg.go.dev/modernc.org/scannertest@v1.0.0
So it seems like pkgsite's backend is having some errors pulling in new versions. CC @jba @julieqiu
I also wonder if the pages could give just a little bit more detail. It's hard to tell what kind of bug this is if all I get is an "oops".
The text was updated successfully, but these errors were encountered:
dup of the pinned #46527 ?
Sorry, something went wrong.
Yes, we continue to have delays. The pinned issue will have progress reports.
I saw that issue but I assumed this was unrelated, since you said "new modules" in that thread and these are not new modules.
Sorry, new module versions.
Duplicate of #46527
No branches or pull requests
For example, https://pkg.go.dev/github.com/ipld/go-ipld-prime@v0.10.0 is a 404 and when I request it via the UI, I just get:
Refreshing just gets me back to the start. This version has been published and requested for hours, so it's not a caching thing.
Someone else has been experiencing the exact same issue on Slack with other modules:
https://pkg.go.dev/modernc.org/qbe@v0.0.6
https://pkg.go.dev/modernc.org/scannertest@v1.0.0
So it seems like pkgsite's backend is having some errors pulling in new versions. CC @jba @julieqiu
I also wonder if the pages could give just a little bit more detail. It's hard to tell what kind of bug this is if all I get is an "oops".
The text was updated successfully, but these errors were encountered: