-
Notifications
You must be signed in to change notification settings - Fork 18k
x/pkgsite: ansipixels disappeared from search results #73242
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
Comments
Thanks! it re-appeared, was there an outage of sort in index/search server? (but other searches worked) btw the page in your sshot is the link that always worked, it's the search that was empty and now indeed works: ![]() any thoughts about that:
https://pkg.go.dev/search?q=set&m=package or https://pkg.go.dev/search?q=sets&m=package for instance don't show even on "more results" and shows a ton of packages completely unrelated to sets but with high import count... maybe the search should try to match the package name or description before the number of imports? feel free to close though if there is no tip - thanks |
cc @golang/pkgsite |
We look at the import path, the description, and the number of importers. |
I expect to see https://pkg.go.dev/fortio.org/sets somewhere I guess it must be a bug for short words matching substrings somewhere or some such |
I think it's because your package has very few importers, compared to the packages that are listed. |
Yes, that's why I was saying
it's difficult for new packages to get discovered (and thus raise their import count) when they don't show up at all so probably a balance should be struck |
What is the URL of the page with the issue?
https://pkg.go.dev/search?q=ansipixels
What is your user agent?
mac chrome but irrelevant afaik
Screenshot
What did you do?
searched for my package by its most common name
What did you expect to see?
my package listed
What did you see instead?
0 and 0 in symbols as well
all this despite
https://pkg.go.dev/fortio.org/terminal/ansipixels#AnsiPixels
having been there since sept 2024 (it used to work, just broke)
while I am it, somehow my packages (fortio.org/*) seems to not show up in search unless I add "fortio" in a prefix, eg "fortio sets" - is there something against vanity URLs ? something I should do on the website for fortio.org or other (I use meta-names to send to the right github location)
The text was updated successfully, but these errors were encountered: