Skip to content

Package search always fails #713

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

Open
justDeeevin opened this issue Jun 4, 2025 · 2 comments · May be fixed by #714
Open

Package search always fails #713

justDeeevin opened this issue Jun 4, 2025 · 2 comments · May be fixed by #714
Labels
bug Something isn't working

Comments

@justDeeevin
Copy link

What happened
When trying to search for packages with noogle, no query ever yields results. This is due to the request to NixOS search's backend returning a 404 error.

Steps to Reproduce
Steps to reproduce the behavior:

  1. Go to https://noogle.dev/pkgs
  2. Search for a package that is known to exist (e.g. vim)
  3. See lack of results

Expected behavior
A list of results from elasticsearch should appear

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: NixOS Unstable
  • Browser Zen Browser (Firefox engine)
  • Version 1.12.10b (Firefox 139.0.1)
@justDeeevin justDeeevin added the bug Something isn't working label Jun 4, 2025
@justDeeevin
Copy link
Author

Rel: nix-community/nh#313. Seems they changed the API versioning spec or something

@justDeeevin
Copy link
Author

More specifically, this has to do with elasticsearch indices. I've seen fixes that either use latest-*-{channel} or latest-43-{channel}. Either way, it seems like someone else is on top of this for nh

justDeeevin added a commit to justDeeevin/noogle that referenced this issue Jun 4, 2025
@justDeeevin justDeeevin linked a pull request Jun 4, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant