10 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	c16e625a08	Say a module's health is not yet judged while its change is under way and until a look after it ... A have said applying and failed for the controller on novox at 15:27:36, from a look at the container being replaced, two seconds before its launch said healthy; the assigner held the canary on it and set novox back. A look now judges only a module that is not in motion, and a module whose composition moved carries unknown until a look after the move.	2026-10-25 15:32:59 +01:00
jschoubben	1cdb4d1a29	Say a module found running on its own have again at the agent's start, so its health is this engine's and not an older engine's unknown ... xorg's have on g14 and shanks kept the unknown an engine before 958ccbd wrote: the baseline believed the have and never handed the module to the session, so no look rewrote its health, and the assigner held every module requiring x11-display back.	2026-10-25 15:27:23 +01:00
jschoubben	958ccbde3e	Say a running module ok once looked at when nothing of it is judged, so mesh-host's canary can be healthy and its other nodes get the new engine (issue 1945)	2026-10-25 11:08:10 +01:00
jschoubben	96d0322498	The node-engine reports reads-wants; a failed apply is said; the have's fingerprint and digest follow its health (R6-A A6)	2026-10-24 16:43:26 +02:00
jschoubben	b2003e7a38	A composition is applied only when the controller or the operator signed it; the node agent's integration tests on an embedded bus (R6-A A9, A1, A5)	2026-10-24 16:42:11 +02:00
jschoubben	1598156752	The node-engine hears no declaration: the queue, orders, put-backs, unsaid, numbers and news go; a session says the facts in the node-engine's own order, and the first have proves a build (R6-A A7, A8)	2026-10-24 16:25:11 +02:00
mesh-tools	150fadfe8b	Write a removal after a restart from the declaration the apply replaced (issue 1369) ... The set of modules this process wrote lives in memory, so a node-engine restarted before the apply that drops a module never wrote that module's removal. The report now names the modules the kept declaration held before, and they are removal candidates.	2026-10-20 01:26:33 +00:00
mesh-tools	6a2fb63bfc	Write a module's have key as removed when the applied declaration no longer holds it (issue 1369) ... A module that left a node kept its have key at running for ever, so nothing could tell it stopped and the gate would never take the seat. The key is written once with the phase removed over the revision read, never deleted. Pins mesh-sdk to the commit that adds the phase.	2026-10-20 01:20:52 +00:00
jschoubben	9d9e3a46c4	Bind the have bucket once per pass, bound by the queue's timeout, and stop the pass at the first error (issue 1132)	2026-10-18 19:18:08 +02:00
jschoubben	0b391f49a2	Write each module's have and the node's own facts beside the report, grouped per module and keyed by the module the controller names (issue 1132) ... The node-engine reads a resource's module and a declaration's builds, says it does in every report (reads_modules), groups the apply's outcome per module with every failing resource named, and writes have.<node>.<module> and have.<node>.node to the bucket only when a value differs, never ahead of or in place of the report (novox/hq ADR 0429 section 4).	2026-10-18 19:10:05 +02:00