novox/mesh-controller
7
0
Fork 0
Code Issues Pull Requests 8 Releases Wiki Activity
Files
6d2e4c299a34fb80ef9c342388a3d31ec519baa8
mesh-controller/cmd
T
History
mesh-admin 6d2e4c299a
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
seat: a push to a named machine waits for the machine's answer, so its call says how it went (issue 629) 
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
..
mesh-builder
Stamp no commit in this repository's own image recipes either (hq issue 363, review of #292)
2026-10-13 06:47:18 +02:00
mesh-controller
seat: a push to a named machine waits for the machine's answer, so its call says how it went (issue 629)
2026-10-13 12:03:53 +00:00