yolo/arr
3
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects Releases Wiki Activity

Score release decks at read time, not at search time #114

New Issue
Closed
opened 2026-08-23 12:16:48 +01:00 by naps62-yolo · 1 comment
naps62-yolo commented 2026-08-23 12:16:48 +01:00
Owner
Copy Link
Copy Source

Observed after #113 deployed: The Batman's release deck still ranks an at-target 1080p (1105) above the 23 GiB 4K (1027). The scores were computed and stored when the deck was last searched, under the old weights; policy tuning never re-ranks an existing deck.

DESIGN.md §5.5 says the numbers are policy rows tuned by hand — that only works if tuning takes effect on what the user sees. The deck endpoints (GET /api/movies/:id/releases, and the series equivalent) should recompute the score with arr_core::score from the stored parsed, size and seeders against the current policy, instead of returning the stored score column.

Keep writing the stored score at search time — the daemon's winner selection at grab time can keep using it. Only the read path changes. The stored seeders count is as stale as the deck itself; that is fine, note it and move on.

Mind the ordering: the API pre-sorts by bucket then score, and the web deck relies on that order — re-sort after rescoring.

Observed after #113 deployed: The Batman's release deck still ranks an at-target 1080p (1105) above the 23 GiB 4K (1027). The scores were computed and stored when the deck was last searched, under the old weights; policy tuning never re-ranks an existing deck. DESIGN.md §5.5 says the numbers are policy rows tuned by hand — that only works if tuning takes effect on what the user sees. The deck endpoints (`GET /api/movies/:id/releases`, and the series equivalent) should recompute the score with `arr_core::score` from the stored `parsed`, `size` and `seeders` against the current policy, instead of returning the stored `score` column. Keep writing the stored score at search time — the daemon's winner selection at grab time can keep using it. Only the read path changes. The stored `seeders` count is as stale as the deck itself; that is fine, note it and move on. Mind the ordering: the API pre-sorts by bucket then score, and the web deck relies on that order — re-sort after rescoring.
naps62-yolo added the area/apidifficulty/easyphase/5-uitype/bug labels 2026-08-23 12:16:59 +01:00
naps62-yolo commented 2026-08-23 12:25:54 +01:00
Author
Owner
Copy Link
Copy Source

Fixed in 9516697 (merged to main): GET /api/movies/:id/releases and GET /api/episodes/:id/releases now recompute the score with arr_core::score::score from the stored parsed, size and seeders against the current policy, and re-sort by bucket then score. The stored score column is untouched at write time, still used by the daemon at grab time.

Fixed in 9516697 (merged to main): `GET /api/movies/:id/releases` and `GET /api/episodes/:id/releases` now recompute the score with `arr_core::score::score` from the stored `parsed`, `size` and `seeders` against the current policy, and re-sort by bucket then score. The stored `score` column is untouched at write time, still used by the daemon at grab time.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
arr-api
 area/ci
CI and test harness
 area/compat
arr-compat
 area/core
arr-core
 area/daemon
arr-daemon
 area/db
arr-db
 area/dl
arr-dl
 area/indexer
arr-indexer
 area/infra
workspace and tooling
 area/meta
arr-meta
 area/parse
arr-parse
 area/probe
arr-probe
 area/subs
arr-subs crate: providers, extraction, translation, sync
 area/web
web/
 difficulty/easy
bounded, obvious approach, few files
 difficulty/hard
subtle correctness or cross-cutting
 difficulty/moderate
multiple files, judgement, an interface to design
 difficulty/trivial
one file, mechanical, no design decisions
 phase/1-skeleton
workspace, CI, config, database, empty API and SPA
 phase/2-logic
parsing and policy engine, pure, no network
 phase/3-sourcing
TMDB and Prowlarr, read-only
 phase/4-movies
movies end to end
 phase/5-ui
search, buckets, library views, queues
 phase/6-tv
seasons, episodes, tracking, derived status
 phase/7-people
owner tags and notifications
 phase/8-compat
Jellyseerr shim
 phase/9-subtitles
build order: subtitles, DESIGN.md §15
 type/bug
type/chore
type/feature
type/test
No labels area/api difficulty/easy phase/5-ui type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
hermes (Hermes (agent)) naps62 (Miguel Palhas) naps62-yolo (naps62-yolo (agent))
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: yolo/arr#114