5 Commits

Include renames

Author	SHA1	Message	Date
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
jschoubben	2cd5550dc7	A stopped tool drops its membership handler and a stopped bundle starts no copy on a call, so a replaced bundle's old tools stay gone (issue 1945, review round 2) ... Its events are refused before the old bundle stops, the bundle watch follows a directory made between its stat and its watch, and a bundle's reason is read without node's colour codes.	2026-10-25 15:44:10 +01:00
jschoubben	d8ac69904d	Refuse an event heard during a reload instead of panicking, and judge a bundle by its entrypoint alone (issue 1945, review) ... An event a module's consumer heard after the module was dropped for a reload read a deleted entry and panicked node-tools, taking every tool on the machine down. The handler now refuses an event of a consumer that is no longer the module's, and a stopped hearing hands nothing on and offers the event again at once. A bundle that writes beside itself (a cache, a socket) loaded itself again after every quiet spell, because the signature took in every file in its directory. A delivery puts every file in place anew, so the entrypoint alone tells a new build. The watch also looks once as it begins, so a bundle that came between its load and the watch is not missed. Tests: 1945/AC23 and AC24 in internal/runtime/reload_test.go, and a stopped hearing in internal/bus/hearing_stopped_test.go.	2026-10-25 15:26:02 +01:00
jschoubben	b0ded57294	Serve a tools bundle as soon as it is in place, changed or gone, with no restart; say why a bundle cannot start (issue 1945) ... node-tools loaded every bundle once at start, so a bundle delivered after it started (mesh-files on shanks, 2026-10-25 12:08) went unserved until a hand restart, and a missing file was said as "not executable". The runtime now watches the entrypoints' directories with inotify, loads a module again once a burst of changes settles, and discovery answers with what is served now. A bundle that cannot start says it does not exist, is not executable with its mode, or the exec error. Tests: 1945/AC19-AC22 in internal/runtime/reload_test.go.	2026-10-25 15:09:49 +01:00