x/pkgsite: cuelang.org/go@v0.14.2 is not rendered three days after being released and proxied

[mvdan]

What is the URL of the page with the issue?

https://pkg.go.dev/cuelang.org/go@v0.14.2

What is your user agent?

Mozilla/5.0 (X11; Linux x86_64; rv:143.0) Gecko/20100101 Firefox/143.0 

Screenshot

What did you do?

Tried seeing the docs for this tagged release. I also tried clicking the "request this version" button a number of times, and half an hour later, the page still shows the same.

What did you expect to see?

The docs should be rendered fine. In fact, they should have been rendered already on my first visit, given that the release is already proxied (https://proxy.golang.org/cuelang.org/go/@v/v0.14.2.info) and it was tagged three days ago.

Earlier versions like https://pkg.go.dev/cuelang.org/go@v0.14.1 rendered just fine.

What did you see instead?

The docs are not rendered at all.

[mvdan]

cc @golang/pkgsite

[mvdan]

Also, we only noticed this because a module user let us know. Is there some way for us to notice if pkgsite fails to render docs for any of the tagged versions for our module? Ideally we would be notified about such issues, so that we can investigate if it's due to a problem on our side, or perhaps a bug on your side that should be fixed.

[gabyhelp]

Related Issues

• x/pkgsite: v0.69.1 page for github.com/IBM/vpc-go-sdk is not loading #74562 (closed)
• x/pkgsite: module not found but is available in proxy #70865 (closed)
• x/pkgsite: package index broken for xiam.li/go-nats #71413 (closed)
• x/pkgsite: pkg.go.dev does not update module version (stuck at v0.0.0) #75330 (closed)
• x/pkgsite: packages with `go 1.21.0` in go line can't be fetch by pkg.go.dev #62031 (closed)
• x/pkgsite: pkg.go.dev don't want to show documentation for the latest version of module #73113 (closed)
• x/pkgsite: new version processing is delayed #46527 (closed)
• x/pkgsite: go package info not updated on every release #40202 (closed)
• x/pkgsite: no docs for gopkg.in/DataDog/dd-trace-go.v1@v1.74.0 #74015 (closed)
• x/pkgsite: @master failed with "could not be found" for an hour #59464

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[mvdan]

The page appears to be available now, one hour after posting this issue. However, I still think this issue needs to be investigated; why wasn't it rendered automatically within three days of publishing and proxying? And why did it not render after we requested the page multiple times in the span of two hours?

[jba]

We are working on reducing the pkgsite backlog.

…

On Mon, Oct 13, 2025 at 6:15 AM Daniel Martí ***@***.***> wrote: *mvdan* left a comment (golang/go#75870) <#75870 (comment)> The page appears to be available now, one hour after posting this issue. However, I still think this issue needs to be investigated; why wasn't it rendered automatically within three days of publishing and proxying? And why did it not render after we requested the page multiple times in the span of two hours? — Reply to this email directly, view it on GitHub <#75870 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AENAOZKLIX27F4X3E2KC6JT3XN3VDAVCNFSM6AAAAACJASIIXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOJWG44TEMJTG4> . You are receiving this because you are on a team that was mentioned.Message ID: <golang/go/issues/75870/3396792137 ***@***.***>

[prattmic]

cc @golang/pkgsite

[ldemailly]

have a similar issue now with #75959 (interestingly yesterday for the first time in months for that same package "fetch" actually worked... but today it's stuck)