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

Decide what a vanished torrent means for its grab #86

New Issue
Closed
opened 2026-08-22 23:35:31 +01:00 by naps62-yolo · 0 comments
naps62-yolo commented 2026-08-22 23:35:31 +01:00
Owner
Copy Link
Copy Source

A grab in sent or downloaded whose infohash Transmission no longer reports is currently left untouched (grab.rs track_sent_grabs, import.rs import_one). Both sites carry a comment deferring the decision to #24; #24 turned out to be about policy hard and soft fails, and a torrent removed by hand is neither, so the decision still has no home.

As it stands the grab row is permanent: the title is not a gap, so it is never re-searched, and the import lane retries it every tick forever.

The decision to make is what an absent torrent means. Most likely: mark the grab failed and reopen the gap without blacklisting anything, since the release did not fail policy. Note that grabs.state = 'failed' also feeds the needs_decision attention queue (DESIGN.md §9.5, "hard-failed twice on different releases"), so a manual removal counted there would be wrong.

Labels: phase/4-movies, area/daemon, difficulty/easy, type/bug

A grab in `sent` or `downloaded` whose infohash Transmission no longer reports is currently left untouched (`grab.rs` `track_sent_grabs`, `import.rs` `import_one`). Both sites carry a comment deferring the decision to #24; #24 turned out to be about policy hard and soft fails, and a torrent removed by hand is neither, so the decision still has no home. As it stands the grab row is permanent: the title is not a gap, so it is never re-searched, and the import lane retries it every tick forever. The decision to make is what an absent torrent means. Most likely: mark the grab `failed` and reopen the gap without blacklisting anything, since the release did not fail policy. Note that `grabs.state = 'failed'` also feeds the `needs_decision` attention queue (DESIGN.md §9.5, "hard-failed twice on different releases"), so a manual removal counted there would be wrong. Labels: `phase/4-movies`, `area/daemon`, `difficulty/easy`, `type/bug`
naps62-yolo added the area/daemondifficulty/easyphase/4-moviestype/bug labels 2026-08-22 23:35:37 +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 Label area/daemon difficulty/easy phase/4-movies type/bug
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#86
Delete Branch "%!s()"

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?