3 Commits

Include renames

Author	SHA1	Message	Date
Daan MeijerandClaude Fable 5.1	1810abd7d8	The tail planner grows a group's open range; ranges:merge-tail packs the slivers ... A round added a row a group whenever 100k articles or 15 minutes had passed, tuned for a tail leased within minutes; with nothing leasing the tail the rows piled up (127k planned tail ranges of a median 14k articles, 97% adjacent). Now a round grows the group's last range when it is a planned, unspooled, untaken row at the tail's priority, up to RANGE_ARTICLES, and only then adds rows; a range taken meanwhile gets the slice as a row. ranges:merge-tail (--dry-run) packs adjacent planned, uncaptured, unspooled, untaken tail ranges of a group and priority into ranges of RANGE_ARTICLES under the lease lock. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-27 10:46:47 +01:00
Daan MeijerandClaude Opus 5.5	fd0f2bde75	Rebuild: the live tail ... coordinator:run plans the articles after each group's last range every TAIL_EVERY_SECONDS (120): one LIST ACTIVE per name prefix gives every group's newest article, and new articles become ranges at priority -1, leased and prefetched before any history. A group gets a tail range once it has TAIL_MIN_ARTICLES (100k, a chunk) new or its last planning is TAIL_MAX_DELAY_MINUTES (15) ago, so quiet groups don't make a range every round. History (planAll, hourly) is now only for groups not planned yet. ranges:plan --tail plans one round. Found on the way: with XFEATURE COMPRESS GZIP on, Eweka compresses LIST ACTIVE's reply too ("215 NewsGroups Follow [COMPRESS=GZIP]"), and listActive waited for a plain end that never came (groups:add --top too). It reads the compressed reply now; the fake server in the test does both. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-09 10:41:16 +02:00
Daan MeijerandClaude Opus 5.5	d5f168d8d2	Rebuild: coordinator (planner, NNTP pool, spool, prefetcher, leases, rule sets), node API and the edge:node worker ... - groups:add / ranges:plan / nodes:create / coordinator:run commands - the node API: lease, the range's chunks as one framed stream from the spool, batches, heartbeat, finish, release (node guard, token per node) - edge:node: needs COORDINATOR_URL and NODE_TOKEN only (placeholders for the rest), posts a batch every 10 chunks, gives its range back on SIGTERM - releases are gathered per batch: 1.04 chunk rows per release at 10 chunks per batch (1.35 when built per XOVER chunk) - partitions are checked per batch instead of remembered Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-09 00:31:06 +02:00