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

Cargo workspace skeleton #1

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

Set up the workspace described in DESIGN.md §11. Empty crates are fine — this
issue is the shape, not the contents.

  • Root Cargo.toml with members = ["crates/*"], [workspace.package],
    [workspace.dependencies] and [workspace.lints] exactly as in §12.
  • All ten crates created, each with [lints] workspace = true and nothing else.
  • rust-toolchain.toml, rustfmt.toml, Justfile with a ci recipe that runs
    the full §12 gate locally.
  • Release profile: lto = "thin", codegen-units = 1.
  • flake.nix following ~/tea/maestro.

Acceptance: just ci passes on an empty workspace.

Labels: phase/1-skeleton, area/infra, difficulty/easy, type/chore

Set up the workspace described in `DESIGN.md` §11. Empty crates are fine — this issue is the shape, not the contents. - Root `Cargo.toml` with `members = ["crates/*"]`, `[workspace.package]`, `[workspace.dependencies]` and `[workspace.lints]` exactly as in §12. - All ten crates created, each with `[lints] workspace = true` and nothing else. - `rust-toolchain.toml`, `rustfmt.toml`, `Justfile` with a `ci` recipe that runs the full §12 gate locally. - Release profile: `lto = "thin"`, `codegen-units = 1`. - `flake.nix` following `~/tea/maestro`. Acceptance: `just ci` passes on an empty workspace. Labels: `phase/1-skeleton`, `area/infra`, `difficulty/easy`, `type/chore`
naps62-yolo added the phase/1-skeletonarea/infradifficulty/easytype/chore labels 2026-08-22 18:22:38 +01:00
naps62-yolo commented 2026-08-22 19:25:25 +01:00
Author
Owner
Copy Link
Copy Source

Done in f4e63f1, direct to `main` (no PR — bootstrap).

Eleven crates including `arr-e2e`, versions and lints pinned once in the root manifest, `Justfile` carrying the §12 gate, nix dev shell, thin-LTO release profile. `just ci` is green in 0.37s warm.

Two judgement calls worth recording:

  • `cargo nextest` exits non-zero on a zero-test run. Rather than `--no-tests=pass`, which would let a broken test filter go green once real tests exist, `arr-core` and `arr-e2e` each carry one placeholder test. Both are to be deleted by the issues that add real tests to those crates.
  • The frontend steps in `just ci` probe for `web/` and no-op until it exists.
Done in f4e63f1, direct to \`main\` (no PR — bootstrap). Eleven crates including \`arr-e2e\`, versions and lints pinned once in the root manifest, \`Justfile\` carrying the §12 gate, nix dev shell, thin-LTO release profile. \`just ci\` is green in **0.37s warm**. Two judgement calls worth recording: - \`cargo nextest\` exits non-zero on a zero-test run. Rather than \`--no-tests=pass\`, which would let a broken test filter go green once real tests exist, \`arr-core\` and \`arr-e2e\` each carry one placeholder test. Both are to be deleted by the issues that add real tests to those crates. - The frontend steps in \`just ci\` probe for \`web/\` and no-op until it exists.
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/infra difficulty/easy phase/1-skeleton type/chore
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#1
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?