mesh-tools

Files

T

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

alive

Say the node tools are there, every minute (hq to-be 45 Phase 1, S11)

2026-10-06 10:06:29 +02:00

announce

Keep what discovery heard when a round hears nothing, and fetch only changed announcements (issue 554)

2026-10-12 13:56:50 +02:00

bus

Bound a state watch's hand-over by its progress, not its whole set, so a large state's newest keys are handed over (issue 1726)

2026-10-24 07:42:08 +02:00

console

Delete merge-check.sh; tests that launch bundles skip with their reason (issue 1295, S2; ADR 0529)