mesh-controller

3 Commits

Include renames

Author	SHA1	Message	Date
jochen	cdaba36eca	Pin the node-engine at its pull request's resumable walk (hq issue 361) mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it… Details mesh/repo-check pass: its merge-check.sh passed Details mesh/delivery-group group fix/361-the-setuid-search-runs-to-completion checking: 1 of 2 member(s) ready Details mesh/delivery superseded: a newer head of the same pull request Details	2026-10-10 01:01:18 +02:00
jochen	eaf5195998	Keep quiet for the setuid search the engine now runs to completion (hq issue 361) The node-engine's search has no bound any more: it runs at idle priority and judges from its last complete, fresh result. The controller's quiet while an agent account waits is the engine's rootsearch.Quiet, not the old fifteen-minute bound, and the node-engine is pinned at its pull request.	2026-10-10 00:54:52 +02:00
jochen	2e1a9abbf7	Count the quiet after a restart from when the controller first saw the search pending mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it… Details mesh/repo-check pass: its merge-check.sh passed Details mesh/delivery failed: its walk failed: a gate on a first machine (what it carried put back), a build, a machine Details The node-engine's own since starts again at every restart, so an agent that restarted the engine in a loop kept agent-can-become-root quiet for ever (the review of 2026-10-09). The controller now keeps when it first saw the verdict waiting for the setuid search (migration 0085), forgets it at the next complete verdict, and raises once the engine's own bound has passed since; the bound and the pending reason are read from mesh-host's rootsearch.	2026-10-09 12:37:18 +02:00