novox/mesh-controller

Hand a mesh of one its store by loopback until a resolver answers its name (issue 701) #325

Open

mesh-admin wants to merge 3 commits from fix/701-a-name-nothing-answers-is-not-used into main

Author	SHA1	Message	Date
jochen	0350b4e222	Judge a mesh of one by the inventory, not by who reads as on the network (issue 701, review 275) mesh/merge-gate out of date: judged against trunk 535c7641ac41, the trunk is now c975dbf7b053; judged again on a recheck or when it is merged Details mesh/repo-check out of date: judged against trunk 535c7641ac41, the trunk is now c975dbf7b053; judged again on a recheck or when it is merged Details mesh/delivery checking Details The network reading leaves out a machine whose assignments cannot be read or whose modules do not resolve, so a bad reading could make a mesh of several look like one and send its machines to loopback. Count the nodes the inventory knows, and every recorded holding and assigned claimant of the resolver seat, before any address filter.	2026-10-14 11:06:56 +02:00
jochen	d53fea31f0	Compose a lone node off the network while nothing answers its name (issue 701) mesh/merge-gate out of date: judged against trunk 04730b54a8f2, the trunk is now 535c7641ac41; judged again on a recheck or when it is merged Details mesh/repo-check out of date: judged against trunk 04730b54a8f2, the trunk is now 535c7641ac41; judged again on a recheck or when it is merged Details mesh/delivery superseded: a newer head of the same pull request Details The first change kept the base references on loopback, and the build agent then failed to publish: its registry is its same-node binding, composed at the node's own internal name. While a mesh of one has no resolver, compose that node without its name, so what it binds to on itself is loopback, as before the network.	2026-10-14 08:58:00 +02:00
jochen	eb99284890	Hand a mesh of one its store by loopback until a resolver answers its name (issue 701) mesh/merge-gate head eb99284890cc merged into trunk 3479a35462b2 — pass: builds mesh-controller → novox; no bus step; every machine composes with the chang… Details mesh/repo-check head eb99284890cc merged into trunk 3479a35462b2 — pass: its merge-check.sh passed Details mesh/delivery superseded: a newer head of the same pull request Details Genesis places the private network at step 21, before anything holds the mesh's resolver seat, and from then the store was named anchor.internal. Nothing answered that name, so the filter's build at step 22 could not pull its base. While the store's node is the only one on the network and no resolver holds the seat, keep answering it loopback, as before the network; a mesh of several, or one with a resolver, is answered as before.	2026-10-14 08:32:15 +02:00