Issues 088, 089 and 090, found fixing 085 #76

2026-09-22T19:58:28Z

jschoubben commented

2026-09-22 19:58:28 +00:00

Three gaps found while fixing issue 085 and in the review of that fix. None is fixed by it; each is its own.

088 — the forge writes its own address, port included, into a container's environment, where the mesh's port placeholder does not resolve. Wrong on any node where the machine port differs, which is most of them.
089 — a module that contributes a route names a port there, and a contributed port is the one reader that does not follow a moved port. The filter opens the port the module listens on while the proxy dials the old one: the service is up, the firewall is right, and the name is dead.
090 — the forge's module cannot take over the forge genesis raises. They differ in container name, network, data directory and the address the forge is told to call itself. Assigning it raises a second forge beside the first, rather than adopting it the way the store and the broker are adopted.

089 matters for the migration: it is exactly the case of an adopted node whose ports were moved because a predecessor holds the usual ones.

Checks pass: records.py, cycle.py, index.py.

Three gaps found while fixing issue 085 and in the review of that fix. None is fixed by it; each is its own. - **088** — the forge writes its own address, port included, into a container's environment, where the mesh's port placeholder does not resolve. Wrong on any node where the machine port differs, which is most of them. - **089** — a module that contributes a route names a port there, and a contributed port is the one reader that does not follow a moved port. The filter opens the port the module listens on while the proxy dials the old one: the service is up, the firewall is right, and the name is dead. - **090** — the forge's module cannot take over the forge genesis raises. They differ in container name, network, data directory and the address the forge is told to call itself. Assigning it raises a second forge beside the first, rather than adopting it the way the store and the broker are adopted. 089 matters for the migration: it is exactly the case of an adopted node whose ports were moved because a predecessor holds the usual ones. Checks pass: `records.py`, `cycle.py`, `index.py`.

jschoubben added 2 commits 2026-09-22 19:58:28 +00:00

Issue 088: the forge's own address names a port it may not have e609ccdbfb

Issues 089 and 090: a contributed route does not follow a moved port; the forge module cannot take over the forge genesis raised 1728765fe3

jschoubben merged commit c46c508c03 into main

2026-09-22 20:00:02 +00:00

jschoubben deleted branch fix/issue-085-followups

2026-09-22 20:00:02 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#76