Raise the assigner's asks on the operator channel, lift a hold once every node runs it healthy, and keep its cause (issue 1906) #40

Merged

mesh-tools merged 3 commits from fix/r6-hold-asks into main 2026-10-25 13:27:30 +00:00

Conversation 1 Commits 3 Files Changed 15

+1048 -50

3 Commits

Author	SHA1	Message	Date
jschoubben	7ef796b04b	Format the assigner's integration test (issue 1906)	2026-10-25 14:16:58 +01:00
jschoubben	ec93585736	Ask a hold again after a restart, leave a merge ask room, take an answer only for its asking (issue 1906, review) ... A hold written again after a lift and a restart reused its first ask id, which the router drops; the hold's time is now its asking. Seven holds could take the router's three places for the teller and keep a merge Approve from being asked; the teller keeps at most two assigner asks open. A release or keep answered for one hold carried over to a later hold of the same fingerprint; an answer now counts only for the asking its warrant names.	2026-10-25 14:15:44 +01:00
jschoubben	6b63f13da6	Raise the assigner's asks on the operator channel, lift a hold once every node runs it healthy, keep the hold's cause (issue 1906) ... Seven modules stayed held on every machine and the operator was never asked: the teller only filled assigner asks from the view, a single failed check held a fingerprint for good, and the held record kept no cause. The teller now asks every assigner ask as it asks merge asks and writes the phone's answer under the ask's key; the assigner lifts a hold whose fingerprint runs healthy on every node that runs the module, says so once and takes its ask back; the held record names health, phase, when and the node's words.	2026-10-25 14:06:58 +01:00