Keep a machine that does not resolve on the private network and in the names, so it is refused alone (issue 1833) #68

Merged

mesh-tools merged 2 commits from fix/1833-one-machine-alone into main

2026-10-22 16:10:23 +00:00

Author	SHA1	Message	Date
jschoubben	bd7731f358	Count a machine that does not resolve and holds a place as on the network for its name and the mesh's sources too (issue 1833) mesh/repo-check head bd7731f3588c merged into trunk 5652312f09d2 beside mesh-controller#437@28a278c1 — pass: its merge-check.sh passed, each part in its to… Details mesh/merge-gate head bd7731f3588c merged into trunk 5652312f09d2 — pass: group fix/1833-one-machine-alone composed: every machine composes with the change … Details mesh/delivery delivered Details mesh/delivery-group group fix/1833-one-machine-alone delivered: every member is delivered Details mesh/check failed: unit: ..test: node:internal/modules/esm/resolve:241 \| bd7731f3588c on 4fac7810a1e4 \| unit 1634 run, 0 kept, 3 skipped \| integration… The tunnel kept such a machine while the names and the packet filter's sources from the mesh, read from their own unchecked resolve, dropped it when that pass refused it too (a seat claimed twice): every other machine was sent the hub as a peer without its name or its address. onTheNetwork keeps it by the same rule as network().	2026-10-22 15:26:48 +02:00
jschoubben	c154bdedd3	Keep a machine that does not resolve on the private network at its place, so one machine's modules refuse only its own declaration (issue 1833) A machine whose own set could not be resolved was left off the private network; when it was the hub, the network could not be composed and every machine's declaration failed. Its placement (key and address) is its last good place and does not change when its modules fail, so it stays on the network and only its own declaration is refused. A refused machine with no place is left off, and a network that cannot be composed from what remains still fails.	2026-10-22 15:03:17 +02:00