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

Reconcile loop skeleton #21

New Issue
Closed
opened 2026-08-22 18:22:39 +01:00 by naps62-yolo · 1 comment
naps62-yolo commented 2026-08-22 18:22:39 +01:00
Owner
Copy Link
Copy Source

DESIGN.md §8. There is no job queue — the database rows are the work list, and
every tick compares desired state to actual state and acts on the gap.

  • Idempotent by construction. Killing the process mid-operation and restarting
    must converge, and there should be a test that does exactly that.
  • Staggered ticks: reconcile 30 s, RSS 10 min, metadata daily, reaper 5 min.
  • Transient state in memory, rebuilt from Transmission on startup.
  • Structured logging per tick: what gap was found, what action was taken. This
    is the only debugging surface when something silently does not download.

This issue is the loop and its scheduling. The individual actions are separate
issues that register into it.

Acceptance: a test that runs several ticks against a seeded database with a
faked Transmission and asserts convergence and idempotence.

Depends on: #4, #7, #3

Labels: phase/4-movies, area/daemon, difficulty/hard, type/feature

`DESIGN.md` §8. There is no job queue — the database rows are the work list, and every tick compares desired state to actual state and acts on the gap. - Idempotent by construction. Killing the process mid-operation and restarting must converge, and there should be a test that does exactly that. - Staggered ticks: reconcile 30 s, RSS 10 min, metadata daily, reaper 5 min. - Transient state in memory, rebuilt from Transmission on startup. - Structured logging per tick: what gap was found, what action was taken. This is the only debugging surface when something silently does not download. This issue is the loop and its scheduling. The individual actions are separate issues that register into it. Acceptance: a test that runs several ticks against a seeded database with a faked Transmission and asserts convergence and idempotence. --- **Depends on:** #4, #7, #3 Labels: `phase/4-movies`, `area/daemon`, `difficulty/hard`, `type/feature`
naps62-yolo added the area/daemondifficulty/hardphase/4-moviestype/feature labels 2026-08-22 18:22:39 +01:00
naps62-yolo self-assigned this 2026-08-22 21:19:32 +01:00
naps62-yolo commented 2026-08-22 21:21:42 +01:00
Author
Owner
Copy Link
Copy Source

Adds a registrable reconcile scheduler in arr-daemon with four independent cadences and an immediate startup reconciliation. Actions receive the database directly and return structured gap/action outcomes; concrete grab, import, RSS, metadata, and reaper behavior remains in their own issues.

The test will seed persistent rows, simulate an external Transmission side effect followed by a crash, rebuild the loop, and verify convergence without a duplicate torrent.

Adds a registrable reconcile scheduler in `arr-daemon` with four independent cadences and an immediate startup reconciliation. Actions receive the database directly and return structured gap/action outcomes; concrete grab, import, RSS, metadata, and reaper behavior remains in their own issues. The test will seed persistent rows, simulate an external Transmission side effect followed by a crash, rebuild the loop, and verify convergence without a duplicate torrent.
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/hard phase/4-movies type/feature
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 naps62-yolo
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: yolo/arr#21
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?