4 Commits

Include renames

Author	SHA1	Message	Date
Daan MeijerandClaude Fable 5.1	ae735361a0	Replay harness: a --to bound and the homelab window driver ... edge-bench --group and replay:corpus take --to <article> next to --from, so a replay covers one window of a group's history while the corpus holds others (the 2016 ranges next to 2021's and 2025's). deploy/replay-window.sh runs a window on homelab: every group whose window ranges are all stored is replayed once into usenet_replay through the voyager-3 app image, 4 groups at a time, looping while the corpus fill completes the rest. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-26 07:56:39 +01:00
Daan MeijerandClaude Fable 5.1	72e973d006	The replay harness: a group's corpus through one carried window into a scratch catalog ... replay:corpus runs edge-bench --group over a group's complete corpus ranges in article order (one window, carried from range to range, finished after the last range; edge/src/lease.rs holds the lease JSON the worker and the bench share) and stores every batch through BatchStore as the worker would, then reports releases finished, provisional, complete and the bytes per header of the NVMe and HDD tables. Refuses a database not named *_replay or *_scratch. The app image carries edge-bench; compose gets a replay profile for homelab. Design amended (REBUILD.md 1, 2, 5): the window is carried by one worker a group, no block leases and no block merger; provisional writes stay for the lease ends. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-26 00:27:09 +01:00
Daan MeijerandClaude Fable 5.1	f8cb17903b	voyager 3: the window in the Rust edge ... The indexer finishes files and releases by posting time instead of the range path: the frontier is the median Date of the last 1,024 plausible dates (within 7 days of it; a run of 1,024 agreeing dates moves it), and a release is finished, judged and written once the frontier is 24 h past its last part, flagged edge when posted within a day of the block's start. At the block's end the rest is written provisionally as edges for the block merger. Files short of parts stay in their release (partial: the store writes complete = false). Gone: fragments and the cut-off, uploads_of (online now), check.ts and the fixture comparison; CI replays the fixtures through edge-bench instead. The wire carries finished, edge and partial. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-25 21:28:35 +01:00
Daan MeijerandClaude Opus 5.5	5109481d67	The Rust worker is the product: edge/, built and checked in CI ... User: Rust is the product (option a). tools/edge-bench-rs moves to edge/ (crate edge; binaries edge-node, the worker, and edge-bench, the replay). CI's new job edge runs cargo test and edge/check-fixtures.sh: both RangeIndexers on three committed captures (edge/fixtures, 25k overview lines each of a.b.models, a.b.ath and a.b.boneless in 5 chunks, 3.5 MB), compared field by field with check.ts; deploy waits for it. The TypeScript RangeIndexer stays as check.ts's reference. README: what it is now; the benchmark findings as history. Random names: looksRandom missed long tokens of capitals and digits ("51294P1CUKR2R35X", release 74539068, readable and a Newznab title). 12+ capitals and digits switching 6+ times between them are random (COD4MW2REMASTERED switches 4 times, BEATLES1964REMASTER twice); both implementations, identical on the fixtures. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-11 20:01:18 +02:00