go: x/pkgsite: packages with `go 1.21.0` in go line can't be fetch by pkg.go.dev
What is the URL of the page with the issue?
- https://pkg.go.dev/github.com/livebud/mux
- https://pkg.go.dev/github.com/livebud/di
- https://pkg.go.dev/github.com/livebud/mod
What is your user agent?
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36
Screenshot
What did you do?
I’ve been releasing quite a few open source Go libraries lately, but I’m having trouble getting docs generated for them.
I’m also having trouble diagnosing if I’m doing something wrong or if it takes ~days to show up on pkg.go.dev.
They all present in the proxy pretty much immediately, so I can download them:
- https://proxy.golang.org/github.com/livebud/mux/@v/v0.0.1.info
- https://proxy.golang.org/github.com/livebud/di/@v/v0.0.1.info
- https://proxy.golang.org/github.com/livebud/mod/@v/v0.0.1.info
The steps I take are:
- Push up a
v0.0.1tag to Github - Request an index
- Come back later
What did you expect to see?
I’d expect when I request an index for it to show up pretty quickly. Within minutes, ideally seconds.
If there was an error, I’d expect an error message with some information on how to resolve it.
What did you see instead?
"github.com/livebud/mod" could not be found.
Thanks for your help!
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 23 (14 by maintainers)
Hi, I’ve looked into this and it looks like there’s a cached negative response for these packages that is preventing them from being fetched. I’ll need more time to dig into it, but it looks like a pkgsite bug.
We did figure out the root cause of the backlogged module processing queue: it was a bug in the proxy that was mitigated by https://go.dev/cl/522183, and should be fixed in the proxy ~today or tomorrow.
It looks like we caught up with backlogged versions over the weekend.
I see the problem: the x/mod dependency of pkgsite is quite old, and doesn’t have the updated go directive syntax.
Fix incoming. We may need to manually reset broken modules; I’ll handle all those listed here, and may write a script to scrape and purge recent modules from the proxy.
Closing as this has been working for a while now.
@Sven-Seyfert it seems pkg.go.dev is not detecting new versions automatically right now. However, you can visit https://pkg.go.dev/github.com/sven-seyfert/gomisc@v0.7.0 (or whatever it is the new version) and request it using the button. I’ve just done it for you and it worked.
Hi @Sven-Seyfert, the fix was deployed, and I just clicked on the button to fetch and got a response (i.e., I didn’t do anything behind the scenes).
You should be able to request v0.5.0 here, and it should work: https://pkg.go.dev/github.com/sven-seyfert/gomisc@v0.5.0
I’ll investigate why versions aren’t flowing.
@david-littlefarmer done
Yes, I’ll manually fix anything folks report here. It’s unfortunately non-trivial to automate.
@hugowetterberg @matthewmueller done.
Ok I believe I’ve re-fetched all versions mentioned in this issue. @Sven-Seyfert I’m still having trouble with yours, presumably because of the capitalization. Needs more investigation.
Change https://go.dev/cl/521125 mentions this issue:
internal/worker: upgrade x/mod to allow fetching 1.21.0 modules