A node says when it composes again, says what a long pass waits on, and composes on request (issue 774) #185

Merged

mesh-tools merged 3 commits from fix/compose-retries-transient into main 2026-10-31 00:21:33 +00:00

Conversation 1 Commits 3 Files Changed 11

+371 -25

3 Commits

Author	SHA1	Message	Date
jschoubben	b0d6684d37	Retry only a failed apply that is not held, answer a repeated compose from the last pass, and say the try the refusal named (issue 774, review round 1) ... The verb compose has no warrant (ADR 0563 §2): Agent.Retry released a module held for a failed backup and re-applied one already running its want. RetryFailed tries again only a failed apply not held, and refuses in words otherwise. A hand ask no longer restarts the growing bound, and a pass less than askedWithin old is the answer, so a caller in a loop drives no passes against the vault. A composer whose loop ended refuses at once. The retry line said try N+1. The test's first shadow now ends before slowAfter is set, a race the race detector found under the new timing.	2026-10-31 01:08:57 +01:00
jschoubben	56eb0b792c	Pin mesh-sdk dfd5d82, so the node-engine announces the verb compose (issue 774)	2026-10-31 00:57:53 +01:00
jschoubben	9c15610f70	Say when the node composes again after a seat that did not answer, say what a long pass waits on, and serve the verb compose (issue 774) ... On 2026-10-31 ace's route-proxy said only that the vault could not be asked, and ace said nothing for five minutes while a pass waited after the vault restarted; the retry that already existed was invisible. A refusal for a seat or a read that did not answer now says when the node composes again ("the node composes again at HH:MM:SS (try N)"), a retry pass says it starts, a pass that runs on says every minute what it waits on, and the node-engine's verb compose makes a pass now and says how it went, so a person recovers without a restart.	2026-10-31 00:56:47 +01:00