compose-candidate reads each manifest once and answers within its bound, from each ask's arrival #200

Merged

mesh-tools merged 4 commits from fix/1126-compose-wait into main 2026-11-03 01:02:32 +00:00

Conversation 3 Commits 4 Files Changed 8

+537 -41

4 Commits

Author	SHA1	Message	Date
jschoubben	df13a83a91	The sandbox composes a node from the input its engine took in, through one shape ... The second sandbox fault of the same kind on mesh-host #200 (postgres's secret reader handed, the module not): the engine stripped the whole catalogue from the input it answers, so the sandbox composed the node's own modules from the indexer's source manifests while the bus reader composes them taken in from their builds (artifacts, templates archive texts, what is handed). Both sides now go through composer.SentInput: the node's own taken-in manifests and kept builds stay in the input, and the sandbox composes them over the cases'. An input past what one bus answer carries is refused in words. A conformance row composes one node through the bus reader and through the sandbox and requires the same declaration. Issue 1126. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-03 01:55:08 +01:00
jschoubben	61a3bd996d	The sandbox composer carries the module the mesh provides itself ... A check that composes with a candidate's own composer (any mesh-host change) gave it the indexer's manifests alone, and the input carries no catalogue, so mesh-wireguard (shipped with mesh-sdk, no repository) was missing: "nothing provides mesh-wireguard / mesh-addressing" on novox for mesh-host #200. Each case now lays the provided module's manifest over its shelf, as the bus reader does. Issue 1126. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-03 01:44:15 +01:00
jschoubben	b8158affa7	compose-candidate is answered off its subscription, so its bound counts from the ask ... An endpoint's subscription hands its asks over one at a time: two checks asking one node at once queued, and the second answered at about 100 s, past the checker's bound and the bus's one-minute reply window. compose-candidate is now answered in a goroutine of its own, at most four at once, one more refused in words. The new cases are rows of the existing tests (test budget). Issue 1126, review round 1. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-03 01:28:45 +01:00
jschoubben	ebb4f4af18	compose-candidate reads each manifest once and answers within the bus's reply window ... Off the control-node an ask of compose-candidate ran into its 60 s bound: each of its two compositions read every manifest in the mesh one key at a time over the bus, on scratch copies of the shadow that kept nothing, so each ask read them all twice again (about 35 s per composition on ace, g14 and shanks; 2 s on novox). The answer at 60 s then came after the bus's one-minute reply window (allow_responses ttl), so the bus refused it and the checker heard nothing. Now the manifests are read eight at a time into the shadow before either composition, a scratch copy keeps what never changes (manifest, archive, done build) in the shadow too, the candidate is laid over a copy taken after the composition without it, and the engine answers within 50 s: unready, naming what it waits on, when not done. Every answer is said in one journal line with its reads and its longest wait. Issue 1126. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-03 01:23:17 +01:00