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

Let a size rejection be waived #210

New Issue
Closed
opened 2026-08-24 21:43:03 +01:00 by naps62-yolo · 0 comments
naps62-yolo commented 2026-08-24 21:43:03 +01:00
Owner
Copy Link
Copy Source

A release rejected on size cannot be waived, so a policy that is wrong about one
title leaves no way through.

§9.3 gives the operator a one-click override on a waived row, and
waiverOverride in web/src/releases.ts implements it for two rules:

case "required_audio": return { allow_english_audio: true };
case "resolution":     return { only_4k: false };

Everything else returns null, so a size rejection renders with no way to
act on it. On Rick and Morty S09 every available pack is rejected on size, which
means the season cannot be grabbed as a pack at all — the release deck shows
three candidates and offers nothing to do with any of them.

That is the case §9.3's override exists for: the operator can see the release,
disagrees with the policy, and takes it anyway on the record.

Add size to the override. The override is written to the title's overrides,
as the other two are, so it is scoped to this title and visible afterwards
rather than being a hidden one-off. Decide what the override says — relaxing the
floor for this title is the obvious shape, but check TitleOverrides and follow
whatever grammar the existing entries use rather than inventing a third.

A waived grab stays a waiver: the row keeps its dashed border, the waiver is
recorded on the import as §5.7 requires, and nothing about this makes the
release eligible for automatic grabbing later.

Note the interaction with #188: if runtime scaling lands, these three S09 packs
stop being rejected at all and this override becomes rarer. It is still worth
having — no band is right for every title, which is the whole reason overrides
exist — but do not justify the feature on the S09 case alone.

Goes through the impeccable skill for the deck side. Drive a real browser with
agent-browser, never google-chrome --headless.

A release rejected on size cannot be waived, so a policy that is wrong about one title leaves no way through. §9.3 gives the operator a one-click override on a waived row, and `waiverOverride` in `web/src/releases.ts` implements it for two rules: ```ts case "required_audio": return { allow_english_audio: true }; case "resolution": return { only_4k: false }; ``` Everything else returns `null`, so a `size` rejection renders with no way to act on it. On Rick and Morty S09 every available pack is rejected on size, which means the season cannot be grabbed as a pack at all — the release deck shows three candidates and offers nothing to do with any of them. That is the case §9.3's override exists for: the operator can see the release, disagrees with the policy, and takes it anyway on the record. Add size to the override. The override is written to the title's `overrides`, as the other two are, so it is scoped to this title and visible afterwards rather than being a hidden one-off. Decide what the override says — relaxing the floor for this title is the obvious shape, but check `TitleOverrides` and follow whatever grammar the existing entries use rather than inventing a third. A waived grab stays a waiver: the row keeps its dashed border, the waiver is recorded on the import as §5.7 requires, and nothing about this makes the release eligible for automatic grabbing later. Note the interaction with #188: if runtime scaling lands, these three S09 packs stop being rejected at all and this override becomes rarer. It is still worth having — no band is right for every title, which is the whole reason overrides exist — but do not justify the feature on the S09 case alone. Goes through the `impeccable` skill for the deck side. Drive a real browser with `agent-browser`, never `google-chrome --headless`.
naps62-yolo added this to the Size bands and waivers milestone 2026-08-24 21:43:03 +01:00
naps62-yolo added the area/webdifficulty/moderatetype/bug labels 2026-08-24 21:43:03 +01:00
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/web difficulty/moderate type/bug
Milestone
No items
No Milestone Size bands and waivers
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#210