Skip to content

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

Closed
ldemailly opened this issue Apr 8, 2025 · 7 comments
Closed

x/pkgsite: ansipixels disappeared from search results #73242

ldemailly opened this issue Apr 8, 2025 · 7 comments
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. pkgsite
Milestone

Comments

@ldemailly
Copy link

ldemailly commented Apr 8, 2025

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

Image

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)

@gopherbot gopherbot added this to the Unreleased milestone Apr 8, 2025
@adonovan
Copy link
Member

I just tried it and got the page you see below. Could you try your query again and report whether it is still failing?

Image

@ldemailly
Copy link
Author

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:

Image

any thoughts about that:

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)

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

@prattmic
Copy link
Member

cc @golang/pkgsite

@prattmic prattmic added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Apr 15, 2025
@jba
Copy link
Contributor

jba commented Apr 15, 2025

We look at the import path, the description, and the number of importers.
What specific packages would you expect to show up for the query "sets"?

@ldemailly
Copy link
Author

I expect to see https://pkg.go.dev/fortio.org/sets somewhere
probably before "assert" and "errors" and "zap" etc... but at least somewhere in the first or last page

I guess it must be a bug for short words matching substrings somewhere or some such

@jba
Copy link
Contributor

jba commented Apr 15, 2025

I think it's because your package has very few importers, compared to the packages that are listed.
Also, the word "set" is very general, so phrases like "a shared set of errors" or "a set of comprehensive testing tools" match.
Those matches plus the large number of importers dominate over the occurrence of the word "set" in the package path.

@jba jba closed this as completed Apr 15, 2025
@ldemailly
Copy link
Author

Yes, that's why I was saying

maybe the search should try to match the package name [or description] before the number of imports?

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. pkgsite
Projects
None yet
Development

No branches or pull requests

5 participants