Say a module's health is not yet judged while it changes, and judge it as soon as its change ends (issue 1945) #141

Merged

mesh-tools merged 3 commits from fix/r6-health-unknown into main 2026-10-25 15:04:54 +00:00

Conversation 1 Commits 3 Files Changed 7

+352 -18

3 Commits

Author	SHA1	Message	Date
jschoubben	b32a27c115	Owe a look when a module's change ends unjudged, so a module with nothing long-running is ok within a look of its apply ... The facts look inside an apply runs while the module is still applying and judges nothing; the running write then left xorg running and unknown until the five-minute statement, holding every x11-display consumer behind it. The running write now nudges the health loop, which looks and says at once. A declaration's report gets the same motion and composition check, and a removed module leaves nothing marked unjudged (review of fix 15).	2026-10-25 15:46:05 +01:00
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