The node-engine fetches every artifact before it replaces anything, and a failed apply no longer claims the old composition runs (issue 1966, recovery) #215

Merged

mesh-tools merged 2 commits from fix/1966-fetch-before-replace into main 2026-11-09 00:16:26 +00:00

Conversation 1 Commits 2 Files Changed 7

+272 -16

2 Commits

Author	SHA1	Message	Date
jschoubben	9f6801a6c5	A module whose apply failed is no longer said to run what it ran (issue 1966, recovery) ... On 2026-11-08 a failed apply of distribution's new build had already replaced its store container, yet the node-engine still held the old build as running, so the put back to it at 23:47 UTC was judged unchanged and applied nothing. A failed apply now marks what runs of the module failed, and a want of the composition that ran before is applied again. Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5	2026-11-09 01:15:13 +01:00
jschoubben	22a37b758c	Fetch every archive and process of an apply before anything is replaced (issue 1966, recovery) ... On 2026-11-08 23:25 UTC the node-engine replaced distribution's store container and only then fetched distribution's program from the store it had just cut off: the module was left half applied and the artifact store unreachable from every other machine. An apply now fetches and checks every archive and process first, as it already pulls a module's images first; one that cannot be had gates its module, so none of its resources is replaced and none of its orphans removed. Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5	2026-11-09 01:14:00 +01:00