mesh-tools

Files

T

jschoubben 331fa06b54 The tool runner reads the memberships state again until it can, instead of giving a module up at its one follow

A JetStream 503 or a timeout at the follow (a bus right after its boot) left the module with no membership for good, since
Follow runs once per module and the stream fallback is gone. The read is now tried again with a growing wait (1 s doubling
to 30 s) until it watches the key or the connection closes; the failure is said once, and its reading once it succeeds.
Tests: none added; a step added to an existing unit test (TestAModuleHearsEveryStreamItsMembershipNames), which fails
without the retry.

(issue 774, 774/S32, review g1 round 1)
Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

2026-11-02 00:51:19 +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

The tool runner reads the memberships state again until it can, instead of giving a module up at its one follow

2026-11-02 00:51:19 +01:00

console

node-tools waits on the self-check's checked, not the controller's (ADR 0571 clause 13, issue 1955)