Release name fixture corpus #9

Closed
opened 2026-08-22 18:22:38 +01:00 by naps62-yolo · 1 comment
Owner

A committed corpus of real release names with expected parses, as the regression
suite for arr-parse.

Pull real names from Prowlarr rather than inventing them — a manual search
against a few indexers gives hundreds in one call. Cover deliberately:

  • Every resolution and source tier in DESIGN.md §5.5.
  • DV-tagged and DV-untagged 4K releases.
  • Multi-audio releases, and the pt-BR markers from §5.2.
  • Names that are simply malformed, which must parse partially rather than fail.

Acceptance: table-driven test, one row per name, failures print the diff.


Depends on: #8

Labels: phase/2-logic, area/parse, difficulty/easy, type/test

A committed corpus of real release names with expected parses, as the regression suite for `arr-parse`. Pull real names from Prowlarr rather than inventing them — a manual search against a few indexers gives hundreds in one call. Cover deliberately: - Every resolution and source tier in `DESIGN.md` §5.5. - DV-tagged and DV-untagged 4K releases. - Multi-audio releases, and the pt-BR markers from §5.2. - Names that are simply malformed, which must parse partially rather than fail. Acceptance: table-driven test, one row per name, failures print the diff. --- **Depends on:** #8 Labels: `phase/2-logic`, `area/parse`, `difficulty/easy`, `type/test`
naps62-yolo added the difficulty/easyarea/parsephase/2-logictype/test labels 2026-08-22 18:22:38 +01:00
Author
Owner

Blocked on a credential. The issue requires pulling real release names from Prowlarr, but no session on this machine can reach its API: prowlarr.n62.casa answers /ping but the API returns 401, there is no Prowlarr API key in ~/.env.claude, the Dokploy file-read API does not expose the container config, and SSH to the Dokploy host is denied.

PR #55 exists with a synthetic corpus and green CI; the reviewer correctly flagged it as out of scope. Holding the PR open. To unblock, drop the key in ~/.env.claude as PROWLARR_API_KEY — the session can then capture real names and replace the fixtures.

Blocked on a credential. The issue requires pulling real release names from Prowlarr, but no session on this machine can reach its API: `prowlarr.n62.casa` answers `/ping` but the API returns 401, there is no Prowlarr API key in `~/.env.claude`, the Dokploy file-read API does not expose the container config, and SSH to the Dokploy host is denied. PR #55 exists with a synthetic corpus and green CI; the reviewer correctly flagged it as out of scope. Holding the PR open. To unblock, drop the key in `~/.env.claude` as `PROWLARR_API_KEY` — the session can then capture real names and replace the fixtures.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: yolo/arr#9