Use policy scoring weights in release search #74
Merged
naps62-yolo
merged 3 commits from 2026-08-22 22:12:18 +01:00
issue/68-core-scoring-wire into main
Labels
Clear labels
area/api
area/ci
area/compat
area/core
area/daemon
area/db
area/dl
area/indexer
area/infra
area/meta
area/parse
area/probe
area/subs
area/web
difficulty/easy
difficulty/hard
difficulty/moderate
difficulty/trivial
phase/1-skeleton
phase/2-logic
phase/3-sourcing
phase/4-movies
phase/5-ui
phase/6-tv
phase/7-people
phase/8-compat
phase/9-subtitles
type/bug
type/chore
type/feature
type/test
arr-api
CI and test harness
arr-compat
arr-core
arr-daemon
arr-db
arr-dl
arr-indexer
workspace and tooling
arr-meta
arr-parse
arr-probe
arr-subs crate: providers, extraction, translation, sync
web/
bounded, obvious approach, few files
subtle correctness or cross-cutting
multiple files, judgement, an interface to design
one file, mechanical, no design decisions
workspace, CI, config, database, empty API and SPA
parsing and policy engine, pure, no network
TMDB and Prowlarr, read-only
movies end to end
search, buckets, library views, queues
seasons, episodes, tracking, derived status
owner tags and notifications
Jellyseerr shim
build order: subtitles, DESIGN.md §15
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: yolo/arr#74
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Replaces the search endpoint placeholder with
arr-corescoring and hydrates score weights from the policy row.\n\nCloses #68.Reviewed
cd9e22e. One finding, on the line below.@@ -476,0 +488,4 @@let score = score(policy,Candidate::PreGrab(&parsed),release.size.unwrap_or_default(),release.size.unwrap_or_default()turns an unknown size into 0 bytes, and the size term then interpolates up from the band floor: with the seeded weights and the 2160p band that is1000 * (0 - 8GiB) / 14GiB = -571, where the old localscore()returned a neutral 0 forNone.The floor rule abstains when the size is unknown (
crates/arr-core/src/policy.rs:226needsSome(size)), so a sizeless release stays eligible but now sorts near the bottom of the eligible bucket.Apply the size term only when the size is known — skip the size component for
Nonerather than scoring it as a zero-byte file.Reviewed
68e404e. No findings — the sizeless case now drops the size term and the new test pins it.