novox/mesh-controller

seat: a push to a named machine waits for the machine's answer, so its call says how it went (issue 629) #301

Merged

mesh-admin merged 3 commits from fix/629-a-push-says-how-it-went into main

2026-10-13 12:44:51 +00:00

Author	SHA1	Message	Date
mesh-admin	ae0b384497	push-wait is untrusted, so it is set in one call like any preference (issue 629) mesh/merge-gate head ae0b384497c2 merged into trunk f3875a6b6019 — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every … Details mesh/repo-check head ae0b384497c2 merged into trunk f3875a6b6019 — pass: its merge-check.sh passed Details mesh/delivery delivered Details The gate warned that the push file asks for a setting without saying whether it is trusted, which makes push-wait terminal-only.	2026-10-13 12:38:31 +00:00
mesh-admin	f09c5ebdec	push: the wait is the call's or the controller's setting push-wait, never a length in the code (issue 629) mesh/merge-gate head f09c5ebdec6c merged into trunk 584aa2d7d7a5 — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every … Details mesh/repo-check head f09c5ebdec6c merged into trunk 584aa2d7d7a5 — pass: its merge-check.sh passed Details mesh/delivery superseded: a newer head of the same pull request Details The operator's rule: a wait is never hard-coded, at most a default is configured. The push verb takes `wait`; without it the controller's setting `push-wait` (module default 2m) applies; a setting that cannot be read waits for nothing, as a push did before, and says so.	2026-10-13 12:09:43 +00:00
mesh-admin	6d2e4c299a	seat: a push to a named machine waits for the machine's answer, so its call says how it went (issue 629) mesh/merge-gate head 6d2e4c299a34 merged into trunk 584aa2d7d7a5 — pass: builds mesh-controller → novox; no bus step; every machine composes with the chang… Details mesh/repo-check head 6d2e4c299a34 merged into trunk 584aa2d7d7a5 — pass: its merge-check.sh passed Details mesh/delivery superseded: a newer head of the same pull request Details The seat ran `push <node> --wait 0`, so a push's call ended at "sent" and nobody learned whether the machine applied it. The caller is answered before a push starts (answersFirst, issue 265), so waiting holds nobody: the call now waits up to two minutes for the machine's own report and keeps it, applied, refused with the machine's reason, or each failed resource with its error.	2026-10-13 12:03:53 +00:00