mesh-tools

183 Commits 1 Branch 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
jochen	424a7eec82	Keep what discovery heard when a round hears nothing, and fetch only changed announcements (issue 554) mesh/merge-gate pass: builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of … Details mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it… Details mesh/delivery delivered Details A round in which no PING reached the laptop's console within the 750 ms window was taken as the mesh's answer that nothing is there, and replaced the index: every seat and module call was refused for five seconds at a time. Discovery now waits up to its patience for a first PING, a round that heard nothing is not kept, a runtime not heard this round is resolved from what it announced last (said with its age), and a round that misses runtimes is logged once. A PING carries a digest of what the instance serves, so an unchanged announcement is not pulled again every round (some 880 kB to the laptop).	2026-10-12 13:56:50 +02:00
jochen	52a0cc4fcb	Forget a runtime's old instance once it answers under a new one, so a restart is not reported as a missed answer	2026-10-05 15:38:30 +02:00
jochen	379d19d907	Wait for every runtime discovery hears from, and name the ones it misses The console gathered $SRV.INFO answers for a fixed 750 ms. The laptop's runtime (48 modules, 341 endpoints, 164 kB) answers last every time: its answer crosses to the broker on another machine and back, a median of 365 ms on a quiet link and 813 ms in one of 25 rounds measured. When it missed the window the console said its modules ran nowhere ("nothing in the mesh is called slack") or only on another machine. Discovery now asks $SRV.PING alongside $SRV.INFO and waits, past the window and up to 5 s, for every instance that answered PING. A runtime that never sends what it serves, or answered before and not now, is named in every answer that might concern it instead of the module being called missing. An answer still too large after first-line descriptions drops them, and says so in its metadata. mesh_runtimes reports, per runtime, its machine, how long its answer took, its size, its modules and tools, whether it was shortened and when it was last heard, and the runtimes and machines not heard.	2026-10-05 15:36:10 +02:00

Author

SHA1

Message

Date

jochen

424a7eec82

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

mesh/merge-gate pass: builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of …

Details

mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it…

Details

mesh/delivery delivered

Details

A round in which no PING reached the laptop's console within the 750 ms window
was taken as the mesh's answer that nothing is there, and replaced the index:
every seat and module call was refused for five seconds at a time. Discovery
now waits up to its patience for a first PING, a round that heard nothing is
not kept, a runtime not heard this round is resolved from what it announced
last (said with its age), and a round that misses runtimes is logged once.
A PING carries a digest of what the instance serves, so an unchanged
announcement is not pulled again every round (some 880 kB to the laptop).

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

jochen

52a0cc4fcb

Forget a runtime's old instance once it answers under a new one, so a restart is not reported as a missed answer

2026-10-05 15:38:30 +02:00

jochen

379d19d907

Wait for every runtime discovery hears from, and name the ones it misses

The console gathered $SRV.INFO answers for a fixed 750 ms. The laptop's
runtime (48 modules, 341 endpoints, 164 kB) answers last every time: its
answer crosses to the broker on another machine and back, a median of
365 ms on a quiet link and 813 ms in one of 25 rounds measured. When it
missed the window the console said its modules ran nowhere ("nothing in
the mesh is called slack") or only on another machine.

Discovery now asks $SRV.PING alongside $SRV.INFO and waits, past the
window and up to 5 s, for every instance that answered PING. A runtime
that never sends what it serves, or answered before and not now, is
named in every answer that might concern it instead of the module being
called missing. An answer still too large after first-line descriptions
drops them, and says so in its metadata.

mesh_runtimes reports, per runtime, its machine, how long its answer
took, its size, its modules and tools, whether it was shortened and when
it was last heard, and the runtimes and machines not heard.

2026-10-05 15:36:10 +02:00