A backup the node agent interrupted runs again, and a held module keeps the build it runs (issue 1289) #189

Merged

mesh-tools merged 2 commits from fix/held-backup into main 2026-10-31 16:33:55 +00:00

Conversation 1 Commits 2 Files Changed 4

+106 -4

2 Commits

Author	SHA1	Message	Date
jschoubben	76c7ddfc52	Keep main's rule for which haves run inside the node's own composition ... Review round 1: a have naming no build in a phase but running is also written for a module that runs inside the node's own (waiting for a yes), so taking it out would drop its resources before the yes. The fp the held have now keeps already fixes postgres (issue 1289); a test drives an interrupted backup end to end. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-10-31 16:38:05 +01:00
jschoubben	39365c62c9	Resume a backup the node agent's own stop interrupted, and keep what a held module runs ... On novox (2026-10-31) postgres's repeat backup was interrupted by the node-engine's restart: its held have named no build, so the node's own composition took postgres in and was refused for its secret reader, and nothing ran the backup again. Issue 1289 (R4c, its delivery held). - A held have names what runs: read from the module's have before backing-up when the agent has no running entry, as the not-composed mark does. - A have in any phase but running that names nothing is not run inside the node's own. - A backup interrupted by the agent's stop is no failure: the next start backs the module up again and applies while the want asks a backup. A real failure stays held for the operator's answer. Quick fix: a new backup ask by hand. Thorough, chosen: the fault fixed where it lives in the node agent, so every data module's interrupted backup resumes by itself. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-10-31 16:33:49 +01:00