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

x/pkgsite: my package doesn't show on the website but can be downloaded #62303

Closed
ayonli opened this issue Aug 26, 2023 · 3 comments
Closed

x/pkgsite: my package doesn't show on the website but can be downloaded #62303

ayonli opened this issue Aug 26, 2023 · 3 comments
Labels
Milestone

Comments

@ayonli
Copy link

ayonli commented Aug 26, 2023

What is the URL of the page with the issue?

https://pkg.go.dev/github.com/ayonli/goext

What is your user agent?

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36

Screenshot

FireShot Capture 002 - github com_ayonli_goext - Go Packages - pkg go dev

What did you do?

I went to the pkg.go.dev and searched for my package, but it did not show on the website.

What did you expect to see?

The package should be shown on the website.

What did you see instead?

package could not be found.

The package is fully viable with the go get or go mod tidy command, this URL https://proxy.golang.org/github.com/ayonli/goext/@v/v0.2.1.info also shows correct information about the package. And the package is actually being used by my other package github.com/ayonli/gorpc, but the website won't show it.

I've hit the Request button, but responded with package could not be found. How is that possible?

@ayonli ayonli added the pkgsite label Aug 26, 2023
@seankhliao seankhliao changed the title ex/pkgsite: my package doesn't show on the website but can be downloaded x/pkgsite: my package doesn't show on the website but can be downloaded Aug 26, 2023
@gopherbot gopherbot added this to the Unreleased milestone Aug 26, 2023
@seankhliao
Copy link
Member

maybe #62031
cc @findleyr

@findleyr
Copy link
Contributor

It's there now. We had a large backlog of modules to burn through after fixing the broken processing. Looks like we caught up over the weekend.

@ayonli
Copy link
Author

ayonli commented Aug 28, 2023

@findleyr Thanks, man, much obliged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants