4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	c46937da04	Apply a module again when the engine holds no record of its resources or its health says one is missing, and move a module with nothing to back up without a backup (issue 1944, issue 1945)	2026-10-25 10:59:21 +01:00
mesh-tools	52600ec7bd	Take the node-engine's parser from mesh-sdk: remaining imports (issue 1392)	2026-10-20 11:17:14 +00:00
jschoubben	62af89f85d	Start no account's manager to look at its units (hq issue 764) ... Every 15 s the failed-units look read the own manager of every account the declaration creates, and reading one is a login that starts it: six module accounts' managers on the control node started and stopped all day, most of its journal. A look only reads (ADR 0240 rule 6) and never asks an account's manager (ADR 0177). An account's manager is read now only when the declaration places a user-scoped unit in it, and only after the machine's own manager says user@<uid>.service is active, as the apply asks before it. A manager not running is said away in the units statement, with no failed units; in liveness its units read unknown with the apply's words, never down. The operator's account on a desktop is still read while logged in, since a module places a user unit there (issue 315's Razer daemon stays said).	2026-10-15 00:33:34 +02:00
jochen	1fc1e74cc3	Judge whether what a module runs stays up, and say it (hq ADR 0240, to-be 48 Phase A) ... A container that crash-looped after its compose applied passed every check the gate had: nothing looked at what a module runs. The node-engine now judges every long-running resource on every look — one read of the runtime, one per service manager — keeps the restarts it counts across recreates and its own restarts, and says the state in every report and as an event on change, again every minute while not healthy. It reads only; nothing is restarted for being unhealthy.	2026-10-07 02:28:15 +02:00