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

Torznab search and RSS client #16

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

DESIGN.md §6.1. Per-indexer Torznab, not Prowlarr's aggregate search API —
the reasoning is in that section and should not be revisited without changing
the design document.

Four call shapes: t=caps, t=search, t=movie with imdbid, t=tvsearch
with tvdbid/season/ep. An empty-query search is the RSS feed; it is the
same endpoint, and that equivalence is what makes §6.2's cost model work.

Torznab XML is Newznab-derived and inconsistent between trackers: optional
attributes, missing sizes, varying seeder fields, occasional invalid XML.
Malformed responses from one indexer must not fail the whole search.

Acceptance: wiremock fixtures recorded from at least three real indexers,
including one with a deliberately broken response.

Depends on: #15

Labels: phase/3-sourcing, area/indexer, difficulty/hard, type/feature

`DESIGN.md` §6.1. Per-indexer Torznab, not Prowlarr's aggregate search API — the reasoning is in that section and should not be revisited without changing the design document. Four call shapes: `t=caps`, `t=search`, `t=movie` with `imdbid`, `t=tvsearch` with `tvdbid`/`season`/`ep`. An empty-query search is the RSS feed; it is the same endpoint, and that equivalence is what makes §6.2's cost model work. Torznab XML is Newznab-derived and inconsistent between trackers: optional attributes, missing sizes, varying seeder fields, occasional invalid XML. Malformed responses from one indexer must not fail the whole search. Acceptance: `wiremock` fixtures recorded from at least three real indexers, including one with a deliberately broken response. --- **Depends on:** #15 Labels: `phase/3-sourcing`, `area/indexer`, `difficulty/hard`, `type/feature`
naps62-yolo added the area/indexerdifficulty/hardphase/3-sourcingtype/feature labels 2026-08-22 18:22:38 +01:00
naps62-yolo self-assigned this 2026-08-22 20:20:58 +01:00
naps62-yolo commented 2026-08-22 20:20:58 +01:00
Author
Owner
Copy Link
Copy Source

Implement the four per-indexer Torznab request shapes behind one typed search request, preserving indexer identity in every result. Parse RSS/Newznab items defensively so optional size, date, download URL, and tracker-specific seeder fields remain optional. Batch searches will return one outcome per indexer so a bad HTTP or XML response stays isolated. Add wiremock coverage using sanitized recordings from three tracker response shapes plus a deliberately malformed response, then run the full just ci gate.

Implement the four per-indexer Torznab request shapes behind one typed search request, preserving indexer identity in every result. Parse RSS/Newznab items defensively so optional size, date, download URL, and tracker-specific seeder fields remain optional. Batch searches will return one outcome per indexer so a bad HTTP or XML response stays isolated. Add wiremock coverage using sanitized recordings from three tracker response shapes plus a deliberately malformed response, then run the full `just ci` gate. <!-- agent-meta: {"model":"gpt-5.6-terra","session":"01a02ae9"} -->
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/indexer difficulty/hard phase/3-sourcing 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#16
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?