6 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	f016c67a72	node-tools: start no bundle again once the runtime itself is stopping (issue 1126) ... The service manager stops node-tools by signalling its whole group, so every bundle gets SIGTERM with it; the launcher took each exit for a fault and started the bundle again, for the 15 s the runtime took to stop. On ace's reboot of 2026-10-28 those restarted bundles dialled the system bus once polkit and the bus had stopped, the bus and polkit came back during the shutdown, nothing stopped them a second time, and the reboot waited 29 minutes on its job timeout. ShutDown, called first on SIGTERM, keeps any bundle from starting again, by a restart or by a call; a running one still answers.	2026-10-28 15:30:12 +01:00
jschoubben	8cdb7c3032	The credential wait's test stays under a second, and a failed watch says the re-read, not a restart (issue 1496) ... Review of 3baeaec: TestAwaitCredential took 1.9 s, over the unit limit; it now sets the watch's settle to 10 ms, writes at 20 ms and gives up at 100 ms (0.2 s). The watch's journal line for a failure named a bundle and a restart; the credential wait now says it is read again every 30 s instead.	2026-10-26 22:18:12 +01:00
jschoubben	3baeaece61	A module's runtime waits for its broker credential and its account at a start, bounded, instead of exiting (issue 1496) ... The node-engine starts a module's runtime before the provisioner's client fills its broker file, and the bus carries a new account only after it reloads its users. The runtime exited on both and was restarted until they were there (ace, 2026-10-26 21:19: mesh-build-node's and mesh-build-image's runtimes exited twice). It now waits up to five minutes from its start, said once: the file is read again each time its directory changes (the bundles' inotify watch, a 30 s backstop), and an authorization refusal is asked again with the backoff. Past the bound it gives up loudly; a file with no url, a pin mismatch and a bad URL stay final.	2026-10-26 22:06:39 +01:00
mesh-tools	33d136e702	Feature 57 (config and provisioning): release mesh-tools (the provider's StateBus, the SDK pin, templates), reviewed	2026-10-16 09:41:17 +00:00
jochen	0307df0850	Say the node tools are there, every minute (hq to-be 45 Phase 1, S11) ... A machine whose node-engine is heard and whose runtime is gone is a machine nobody can ask anything, and nothing said so. The runtime now says on mesh.control.<node>.tools-alive, every minute, that it is there, with its interval and build; the controller raises tools-silent after three missed. Core NATS, like the host's heartbeat: a lost one is the next one. A heartbeat the bus refuses is logged when that starts and when it stops.	2026-10-06 10:06:29 +02:00
jochen	e45389f75a	node-tools in Go: the node's runtime, launch-only, wire-compatible with the TypeScript (hq ADR 0193) ... The runtime knows no language, so nothing ties it to Node.js. This ports its serve mode — the pinned bus connection and patient connect, following memberships, launching every served bundle over MCP on stdio with its own environment, a child's emit published as its module, each tool, the tools verb and seat verbs served where the mesh issued them, and the console on loopback — to one static binary. Same subjects, request and reply bodies, event headers and MCP answers. The TypeScript stays: it is still the runtime inside the per-module containers until WP4c. Tests run against a real bus and share the TypeScript fixtures.	2026-10-03 21:21:52 +02:00