Issues 229 and 230: a rollout cannot be followed through the mesh's tools; a host hand-over loses its report and a plan waits for ever #352

2026-10-04T08:51:51Z

mesh-admin commented

2026-10-04 08:51:51 +00:00

Two issues from rolling out to-be 41.

229. Three times, an agent had to post JSON-RPC by hand to the node console: to wait for a plan (plans answers once, in prose), to read status (prose and JSON in one string), and to read one module out of module list. The fix needs a way to wait, and structured answers.
230. A host handing over to a newly delivered version loses that apply's report. Issue 163 left that mechanism in place: standing aside cancels the report's context. The plan waiting on it then waits for ever, while showing "late": false and "for 0s", and nothing logs or alerts. It was found by asking twice and reading a machine's journal, and released by pushing the three machines. The fix: report before standing aside, and give a plan's wait a real age and a bound, with lateness said in status, in the log, and as an event.

records.py, cycle.py and index.py pass.

Two issues from rolling out to-be 41. - **229.** Three times, an agent had to post JSON-RPC by hand to the node console: to wait for a plan (`plans` answers once, in prose), to read `status` (prose and JSON in one string), and to read one module out of `module list`. The fix needs a way to wait, and structured answers. - **230.** A host handing over to a newly delivered version loses that apply's report. Issue 163 left that mechanism in place: standing aside cancels the report's context. The plan waiting on it then waits for ever, while showing `"late": false` and "for 0s", and nothing logs or alerts. It was found by asking twice and reading a machine's journal, and released by pushing the three machines. The fix: report before standing aside, and give a plan's wait a real age and a bound, with lateness said in `status`, in the log, and as an event. `records.py`, `cycle.py` and `index.py` pass.

mesh-admin added 1 commit 2026-10-04 08:51:51 +00:00

Issue 229: a rollout cannot be followed through the mesh's tools 8d83d94659

jschoubben added 1 commit 2026-10-04 08:54:39 +00:00

Issue 230: a host that hands over loses its report, and a plan waits for it for ever without saying so 2db0ea268d

mesh-admin changed title from ~~Issue 229: a rollout cannot be followed through the mesh's tools~~ to Issues 229 and 230: a rollout cannot be followed through the mesh's tools; a host hand-over loses its report and a plan waits for ever

2026-10-04 08:54:45 +00:00

jschoubben added 1 commit 2026-10-04 09:00:16 +00:00

Issue 229: new tools never reach an agent's connection, and the console's generic tools are not on it 9c13c89fa3

jschoubben added 1 commit 2026-10-04 09:00:29 +00:00

Issue 230: a report is also lost when the apply restarts the bus f23a71e0d7

jschoubben added 1 commit 2026-10-04 09:01:53 +00:00

Issue 229: the stale tool list is a connection opened before discovery; the fix is list-changed 0c2eae07c5

mesh-admin merged commit d2689c0f86 into main

2026-10-04 10:09:35 +00:00

mesh-admin deleted branch issues/229-a-rollout-cannot-be-followed-through-the-meshs-tools

2026-10-04 10:09:35 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#352