feat(search): add backend-scoped global search - #111
Merged
Conversation
github-actions
Bot
force-pushed
the
feature/global-search
branch
from
July 26, 2026 21:08
ecf6f7d to
45d2fbf
Compare
github-actions
Bot
force-pushed
the
feature/global-search
branch
from
July 26, 2026 21:14
ca43ed4 to
0aeabb5
Compare
github-actions
Bot
force-pushed
the
feature/global-search
branch
from
July 26, 2026 21:17
42961cf to
a4043a7
Compare
github-actions
Bot
force-pushed
the
feature/global-search
branch
from
July 27, 2026 03:48
c0c7c17 to
67adf21
Compare
hotzenplotz5
marked this pull request as ready for review
July 27, 2026 03:53
This was referenced Jul 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Architecture
Normal search GETs use the existing database through a dedicated
PRAGMA query_only=ONconnection. The browser never calls TVScraper, TMDB, IMDb, RESTfulAPI, SVDRP or SuiteBridge, and search performs no provider resolution.Search performance hardening
The initial mobile test exposed a real latency problem with 174,164 persisted EPG events. The former query evaluated provider JSON and correlated person subqueries for each event and repeated the scan for count and result selection.
The final implementation now:
A regression fixture searches 174,164 synthetic EPG events for both
Pulp FictionandJohn Travoltaand enforces a bounded runtime. Local measurements were approximately 0.1 seconds for those targeted searches and below 0.8 seconds for a deliberately broad two-character query.API
hasMoreFrontend
AbortController, request-generation guard and 12-second timeoutAufnahmen,EPGand optional person summariesThe VDR remote and EPG timeline are unchanged. The old recording browser is not used.
PR #101 assessment
The conflicting old patch was not copied. Current
mainalready has the consistent 128-person / 65,535-byte contract and its regression model keeps all 52Pulp Fictionpeople, including John Travolta beyond the former 12-person cutoff. A future increase must update plugin, transport, backend parser and tests together.Validation
Passed locally and in the publishing workflow:
make test-global-searchmake test-docsgit diff --checkPreviously completed targeted validation also covers API routing, HTTP/install staging, Recordings 2, genre frontend, VDR remote, EPG timeline and daemon compilation paths. GitHub Actions is triggered again on the final one-commit branch.