4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	3d1a450406	pacman starts a round's run only once the node's file holds the round's mirror list, and a refresh never writes after a round opened (ADR 0585 §2, §4; review round 1) ... The opener ranked the list and took its turn in the same step, so its upgrade started before the keeper's change hook wrote /etc/pacman.d/mirrorlist, and a failed write on any node was only logged. A round's run now writes the list first and checks the file holds the revision the round opened with; otherwise the run is refused with why and tried again an hour later, as every refused run is. A refresh asks again for a running round right before its write, since ranking takes minutes. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-01 16:32:59 +01:00
jschoubben	2b495c4818	pacman keeps one mirror list for the mesh, ranked in the write that opens each round and written by every node (ADR 0585, issue 1876) ... Each node's reflector ranked its own list on its own timer, and on 2026-10-31 one node's lagging first mirror left it a Node.js version behind the rest. The list is now the module's state mirrors, key list: the node that opens a week's round ranks it with the module's reflector options, keeps only mirrors whose last sync is no older than the newest found, and the round's key names the list's revision. Every keeper writes /etc/pacman.d/mirrorlist whole from the key through the root helper's new verb mirrorlist, when the key changes and when the file differs, and never writes an empty or unreadable list. reflector.timer is declared stopped and disabled, and reflector.conf saves nothing. pacman_mirrors answers the shared list, its ranker and age and whether this node's file matches; with refresh it asks this node's keeper to rank again, refused while a round runs, naming it. The round's integration test proves the opening write and both nodes' files. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-01 16:18:22 +01:00
jschoubben	276422a85b	issue 1841/S8: join the round to the keeper's loop, so a node starts the moment the node before it passed and a pass is answered from the operator's channel	2026-10-22 17:35:36 +02:00
jschoubben	d70135bf08	issue 1841/S5: join the upgrade parts to the keeper's loop, so a node's log, records, unfinished runs and asks are taken up by its own keeper ... At its start the keeper reads the log into runs once, prunes old records and carries unfinished runs on; after every released lock it carries them on again; it takes each ask at <node>.* and prunes records daily. The root helper's client is a constructor (newRootActs) the helper replaces; until then every act is refused, named.	2026-10-22 14:39:59 +02:00