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

Error 500 when searching for any keyword on ubuntu.com/security/notices #14049

Open
pnwAlex opened this issue Jul 5, 2024 · 3 comments
Open

Comments

@pnwAlex
Copy link

pnwAlex commented Jul 5, 2024

Summary

Error 500 when searching for a keyword on https://ubuntu.com/security/notices

Steps to reproduce the behavior

  1. Go to https://ubuntu.com/security/notices
  2. In the "Details contain" field, type anything, such as "gcc" or "Apache"
  3. Click the "Search" button
  4. Get an error message:
    500: Server error
    Something's gone wrong.
    The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
    Try reloading the page. If the error persists, please note that it may be a known issue. If not, please file a new issue.

Expected behavior

It should find any security notices containing the keyword you searched for.

Screenshot

image

Browser/device details

  • Device: Windows PC and MacBook
  • OS: Windows 10 and macOS 14.5
  • Browser [e.g. stock browser, safari]: Firefox 115.12.0esr and Google Chrome v126 on macOS and Windows 10
  • Version [e.g. 22]: Firefox 115.12.0esr, Chrome 126
@Grissess
Copy link

Grissess commented Jul 9, 2024

Replicated the issue on a local MacBook, Firefox 127.0.2 on 64-bit M1 (though I imagine this is serverside :)

This occurs during a search for any non-empty string.

@hagai-helman
Copy link

Same for me (Firefox 127.0.2 (64-bit) on Ubuntu 24.04).

Also happens when the search string (details) is empty, for most combinations of release and offset (i.e. page number). Interestingly enough, not for all combinations. For example, order=newest&release=mantic&details=&offset=10 works fine.

@seva-luchianov
Copy link

Potentially related to #14018, I assume the entire API is borked in the backend with relation to query strings

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

No branches or pull requests

4 participants