Cite the hq issues by the numbers they were given: 285, 286, 287
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 (0 of …
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery superseded: a newer head of the same pull request

This commit is contained in:
jochen
2026-10-07 02:00:11 +02:00
parent dac4d423a8
commit 0a5dbc7e9a
3 changed files with 4 additions and 4 deletions
+1 -1
View File
@@ -30,7 +30,7 @@ bundleless=""
if ! command -v node >/dev/null 2>&1 || [ ! -d node_modules/@novox/mesh-sdk ]; then
echo "NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk"
packages=$(printf '%s\n' "$packages" | grep -v -e '/internal/runtime$' -e '/internal/console$')
# What of the console launches no bundle runs anyway: how an address resolves (novox/hq issue 284).
# What of the console launches no bundle runs anyway: how an address resolves (novox/hq issue 287).
bundleless='^TestASeatAndAModuleOfOneNameAreEachReached$'
fi
if command -v gcc >/dev/null 2>&1; then
+2 -2
View File
@@ -337,7 +337,7 @@ func indexOfEndpoints(endpoints []announce.Endpoint) (*index, map[string]map[str
// <module>.<tool>, or seat:<seat>.<verb>, → index in l.Tools. **Apart**, because a seat and a module may
// share a name — mesh-delivery is the delivery's seat and the module holding it (novox/hq ADR 0239), and
// the module answers the seat's verbs with tools of the same names: in one namespace the module's tool
// took the key first, and the seat was listed with no verb at all (novox/hq issue 284).
// took the key first, and the seat was listed with no verb at all (novox/hq issue 287).
toolAt := map[string]int{}
machines := map[string]bool{}
for _, e := range endpoints {
@@ -450,7 +450,7 @@ func resolve(x *index, address string) (target, error) {
s := x.seat(prefix)
if s != nil && x.Modules[prefix] != nil && findTool(x.Modules[prefix].Tools, name) != nil {
// **A seat and a module of one name** (novox/hq issue 284): mesh-delivery is the delivery's seat and
// **A seat and a module of one name** (novox/hq issue 287): mesh-delivery is the delivery's seat and
// the module holding it. The module's tool is meant when the seat has no such verb, or when a machine
// is named for a seat held once for the mesh — `<node>/<module>.<tool>` is a module on one machine.
if findTool(s.Verbs, name) == nil || (node != "" && s.Scope != "node") {
+1 -1
View File
@@ -7,7 +7,7 @@ import (
"github.com/novox/mesh-tools/node-tools/internal/announce"
)
// **Issue 284**: mesh-delivery is the delivery's seat, held once for the mesh, and the module holding it,
// **Issue 287**: mesh-delivery is the delivery's seat, held once for the mesh, and the module holding it,
// which answers the seat's verbs with tools of the same names and has tools of its own. Discovery put the
// module's tool and the seat's verb under one key, so the seat was listed with no verb; and every address
// with the name resolved to the seat — `mesh-delivery.deliveries` and `novox/mesh-delivery.delivery_status`