Bug 16474 - error-report-web: refactor Search box to (1) make it actually work (2) allow more fine-grained queries
Summary: error-report-web: refactor Search box to (1) make it actually work (2) allow ...
Status: NEW
Alias: None
Product: Error Reporting tool
Classification: Yocto Project Subprojects
Component: Error Reporting Tool (show other bugs)
Version: 6.2
Hardware: All Multiple
: Medium+ enhancement
Target Milestone: 6.2 M2
Assignee: Tim Orling
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2026-10-29 19:06 UTC by Tim Orling
Modified: 2026-10-29 19:08 UTC (History)
0 users

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Orling 2026-10-29 19:06:11 UTC 
Related to #6541 and #9651.

Because of the sheer size of the database now, the Search box will never complete before the gunicorn (or uwsgi) timeout, which hangs to browser and is a TERRIBLE UX. Enforcing a shorter timeout (10 seconds) in Django works, but will also NEVER return a result, regardless of the input text in the Search box. Finer-grained queries using additional URL terms works fine, especially since halstead indexed the database.

What we need is to look at layerindex-web and see how the Search is working there and borrow ideas to refactor error-report-web. While we are at it, adding conditionals like AND/OR as mentioned in #6541 is a very reasonable ask and layerindex-web already has some of that capability.