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

Use policy scoring weights in release search #74

Merged
naps62-yolo merged 3 commits from issue/68-core-scoring-wire into main 2026-08-22 22:12:18 +01:00
Conversation 2 Commits 3 Files Changed 2
+123 -46
naps62-yolo commented 2026-08-22 21:46:21 +01:00
Owner
Copy Link
Copy Source

Replaces the search endpoint placeholder with arr-core scoring and hydrates score weights from the policy row.\n\nCloses #68.

Replaces the search endpoint placeholder with `arr-core` scoring and hydrates score weights from the policy row.\n\nCloses #68.
naps62-yolo added 2 commits 2026-08-22 21:46:21 +01:00
fix(api): use policy scoring weights 19342d70e8
Merge remote-tracking branch 'origin/main' into issue/68-core-scoring-wire
ci / web (pull_request) Successful in 29s
Details
e2e / e2e (pull_request) Successful in 52s
Details
ci / rust (pull_request) Successful in 4m9s
Details
cd9e22e410
naps62-yolo reviewed 2026-08-22 21:48:40 +01:00
naps62-yolo left a comment
Author
Owner
Copy Link
Copy Source

Reviewed cd9e22e. One finding, on the line below.

Reviewed `cd9e22e`. One finding, on the line below. <!-- agent-meta: {"model":"claude-opus-5","session":"298dcd6d"} -->
crates/arr-api/src/search.rs
@@ -476,0 +488,4 @@
let score = score(
policy,
Candidate::PreGrab(&parsed),
release.size.unwrap_or_default(),
naps62-yolo commented 2026-08-22 21:48:40 +01:00
Author
Owner
Copy Link
Copy Source

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 is 1000 * (0 - 8GiB) / 14GiB = -571, where the old local score() returned a neutral 0 for None.

The floor rule abstains when the size is unknown (crates/arr-core/src/policy.rs:226 needs Some(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 None rather than scoring it as a zero-byte file.

`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 is `1000 * (0 - 8GiB) / 14GiB = -571`, where the old local `score()` returned a neutral 0 for `None`. The floor rule abstains when the size is unknown (`crates/arr-core/src/policy.rs:226` needs `Some(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 `None` rather than scoring it as a zero-byte file. <!-- agent-meta: {"model":"claude-opus-5","session":"298dcd6d"} -->
naps62-yolo marked this conversation as resolved
naps62-yolo added 1 commit 2026-08-22 21:51:03 +01:00
fix(api): skip unknown release size score
ci / rust (pull_request) Successful in 1m31s
Details
ci / web (pull_request) Successful in 39s
Details
e2e / e2e (pull_request) Successful in 1m40s
Details
68e404ed07
naps62-yolo reviewed 2026-08-22 21:51:30 +01:00
naps62-yolo left a comment
Author
Owner
Copy Link
Copy Source

Reviewed 68e404e. No findings — the sizeless case now drops the size term and the new test pins it.

Reviewed `68e404e`. No findings — the sizeless case now drops the size term and the new test pins it. <!-- agent-meta: {"model":"claude-opus-5","session":"298dcd6d"} -->
naps62-yolo merged commit b5413eef46 into main 2026-08-22 22:12:18 +01:00
naps62-yolo deleted branch issue/68-core-scoring-wire 2026-08-22 22:12:18 +01:00
Sign in to join this conversation.
Reviewers
No Reviewers
naps62-yolo
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 Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
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#74
Delete Branch "issue/68-core-scoring-wire"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?