novox/mesh-catalog
13
0
Fork 0
Code Issues Pull Requests 4 Actions Packages Projects Releases Wiki Activity

Serve postgres's consumers the port its server is published on, not the container's 5432 (issue 957) #339

Merged
mesh-tools merged 1 commits from fix/957-postgres-serves-published-port into main 2026-10-16 20:15:34 +00:00
Conversation 4 Commits 1 Files Changed 4
+66 -20
mesh-tools commented 2026-10-16 20:08:29 +00:00
Member
Copy Link
Copy Source

Issue 957 (critical): since 21:49 gitea and keycloak on novox could not reach postgres. Once issue 954 let the provisioner client fill their files from postgres's bound entry, the entry served port 5432 — the container's own (moved.go servedPort = 5432) — while postgres is published 6852:5432 on novox. Service is restored meanwhile by a temporary redirect on novox (nft table hotfix957), to be removed once this is delivered.

Fix (deb2020b): the client's existing port rule moves unchanged into portFromEnv (MESH_POSTGRES_PORT, else MESH_PROVISION_POSTGRES_PORT unless unfilled, else the MESH_PROVISION_POSTGRES URL's port — ${port:5432}, filled with the machine's published port — else 5432); moved() serves publishedPort(os.Getenv). Test published_port_test.go.

Reviewed by review-awg@novox (larger model): approve. Per ADR 0398 the merge waits for the operator's Approve.

Issue 957 (critical): since 21:49 gitea and keycloak on novox could not reach postgres. Once issue 954 let the provisioner client fill their files from postgres's bound entry, the entry served `port` 5432 — the container's own (moved.go `servedPort = 5432`) — while postgres is published 6852:5432 on novox. Service is restored meanwhile by a temporary redirect on novox (nft table hotfix957), to be removed once this is delivered. Fix (deb2020b): the client's existing port rule moves unchanged into `portFromEnv` (MESH_POSTGRES_PORT, else MESH_PROVISION_POSTGRES_PORT unless unfilled, else the MESH_PROVISION_POSTGRES URL's port — `${port:5432}`, filled with the machine's published port — else 5432); `moved()` serves `publishedPort(os.Getenv)`. Test published_port_test.go. Reviewed by review-awg@novox (larger model): approve. Per ADR 0398 the merge waits for the operator's Approve.
mesh-tools added 1 commit 2026-10-16 20:08:29 +00:00
Serve postgres's consumers the port its server is published on, not the container's 5432 (issue 957)
mesh/merge-gate head deb2020bd47d merged into trunk 5652a1494493 — pass: builds postgres, sent nowhere; no bus step; 2 wait(s) for a person; every machine …
Details
mesh/repo-check head deb2020bd47d merged into trunk 5652a1494493 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…
Details
mesh/delivery delivered
Details
deb2020bd4 
On novox postgres is published 6852:5432; handed 5432, gitea and keycloak reached
nothing once their files were filled from postgres's entry.
mesh-tools commented 2026-10-16 20:08:35 +00:00
Author
Member
Copy Link
Copy Source

Delivery novox/mesh-catalog@deb2020bd47d — delivered since 2026-10-16T20:18:53Z

Delivery plan — builds postgres, sent nowhere; no bus step; 2 wait(s) for a person

  • tier 0: postgres
  • ace: waits for a person: postgres
  • novox: waits for a person: postgres
  • postgres waits for a person: its policy records (module) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends
  • postgres provides postgres-database: its consumers are sent again after it
  • postgres keeps data (ADR 0233): what it holds is backed up before it moves

Machines

  • postgres on every machine running it: sent

Transitions

  • 2026-10-16 20:08 (new) → proposed (announced): novox/mesh-catalog#339's head announced
  • 2026-10-16 20:11 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-16 20:11 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-16 20:12 ready → proposed (recheck): its check was never asked (not in the build queue 3 minutes after the head was announced); issue 957 is critical
  • 2026-10-16 20:15 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-16 20:15 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-16 20:15 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-16 20:15 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
  • 2026-10-16 20:18 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@deb2020bd47d` — **delivered** since 2026-10-16T20:18:53Z **Delivery plan** — builds postgres, sent nowhere; no bus step; 2 wait(s) for a person - tier 0: postgres - ace: waits for a person: postgres - novox: waits for a person: postgres - postgres waits for a person: its policy records (module) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends - postgres provides postgres-database: its consumers are sent again after it - postgres keeps data (ADR 0233): what it holds is backed up before it moves **Machines** - postgres on every machine running it: sent **Transitions** - 2026-10-16 20:08 (new) → proposed (announced): novox/mesh-catalog#339's head announced - 2026-10-16 20:11 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 20:11 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-16 20:12 ready → proposed (recheck): its check was never asked (not in the build queue 3 minutes after the head was announced); issue 957 is critical - 2026-10-16 20:15 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 20:15 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-16 20:15 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-16 20:15 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-16 20:18 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh-tools added the mesh/ready label 2026-10-16 20:08:39 +00:00
mesh-tools commented 2026-10-16 20:08:39 +00:00
Author
Member
Copy Link
Copy Source

ready at deb2020bd4

Reviewed by review-awg@novox: approved by review-awg: postgres serves its published port, the client's port rule unchanged (issue 957, critical). Marked through mesh-delivery.mark-ready (novox/hq issue 913).

ready at deb2020bd47dcf68e3ec313ab6cbf219af2883e0 Reviewed by review-awg@novox: approved by review-awg: postgres serves its published port, the client's port rule unchanged (issue 957, critical). Marked through mesh-delivery.mark-ready (novox/hq issue 913).
mesh-tools commented 2026-10-16 20:11:57 +00:00
Author
Member
Copy Link
Copy Source

Merge check at deb2020b
Judged: head deb2020bd47d merged into trunk 5652a1494493; read beside it: mesh-controller 53a3c91f53ce, mesh-controller-main 53a3c91f53ce, mesh-host cd13f7726ef0, mesh-tools 7412c5b6c9c5

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: postgres)
  • mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds postgres, sent nowhere; no bus step; 2 wait(s) for a person

  • tier 0: postgres
  • ace: waits for a person: postgres
  • novox: waits for a person: postgres
  • postgres waits for a person: its policy records (module) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends
  • postgres provides postgres-database: its consumers are sent again after it
  • postgres keeps data (ADR 0233): what it holds is backed up before it moves
  • read by no module's build: modules/postgres/cmd/postgres-provider/published_port_test.go

Run by the build seat on shanks as build-1792181310678111096 (builds --log build-1792181310678111096).

--- the gate: postgres
postgres: ok, keeps state bound, reads mesh-controller.assignments, keeps store (valuable), dumps (rebuildable), ready: server by tcp on database every 30s
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-16T19:55:20Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-16T19:55:20Z

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): postgres

notes:
  - modules/postgres/cmd/postgres-provider/published_port_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.003s
words: 12 retired words and 70 daemons' lines, none in the 53204 strings of 799 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.013s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/mailstore	0.009s
mail-store: claimed only by mesh-mail
ok  	git.novox.be/novox/mesh-catalog/checks/secrets	0.014s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
ok  	git.novox.be/novox/mesh-catalog/checks/predefined	0.263s
predefined.json: 2 key(s), none removed that a module names
ok  	git.novox.be/novox/mesh-catalog/checks/config	0.016s
config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved)
ok  	git.novox.be/novox/mesh-catalog/checks/templates	0.012s
templates: no module keeps a file's text inline but the 0 listed
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 61, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.219s
testing modules/postgres
ok  	postgres/cmd/postgres-provider	1.101s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `deb2020b` Judged: head `deb2020bd47d` merged into trunk `5652a1494493`; read beside it: mesh-controller `53a3c91f53ce`, mesh-controller-main `53a3c91f53ce`, mesh-host `cd13f7726ef0`, mesh-tools `7412c5b6c9c5` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: postgres) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds postgres, sent nowhere; no bus step; 2 wait(s) for a person - tier 0: postgres - ace: waits for a person: postgres - novox: waits for a person: postgres - postgres waits for a person: its policy records (module) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends - postgres provides postgres-database: its consumers are sent again after it - postgres keeps data (ADR 0233): what it holds is backed up before it moves - read by no module's build: modules/postgres/cmd/postgres-provider/published_port_test.go Run by the build seat on shanks as `build-1792181310678111096` (`builds --log build-1792181310678111096`). ``` --- the gate: postgres postgres: ok, keeps state bound, reads mesh-controller.assignments, keeps store (valuable), dumps (rebuildable), ready: server by tcp on database every 30s long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-16T19:55:20Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-16T19:55:20Z machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): postgres notes: - modules/postgres/cmd/postgres-provider/published_port_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.003s words: 12 retired words and 70 daemons' lines, none in the 53204 strings of 799 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/mailstore 0.009s mail-store: claimed only by mesh-mail ok git.novox.be/novox/mesh-catalog/checks/secrets 0.014s secrets: no setting can replace a vault secret in a mergeable file (1 known, nested) ok git.novox.be/novox/mesh-catalog/checks/predefined 0.263s predefined.json: 2 key(s), none removed that a module names ok git.novox.be/novox/mesh-catalog/checks/config 0.016s config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved) ok git.novox.be/novox/mesh-catalog/checks/templates 0.012s templates: no module keeps a file's text inline but the 0 listed ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 61, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.219s testing modules/postgres ok postgres/cmd/postgres-provider 1.101s --- its merge-check-typescript.sh (typescript toolchain) ```
mesh-tools commented 2026-10-16 20:15:27 +00:00
Author
Member
Copy Link
Copy Source

Merge check at deb2020b
Judged: head deb2020bd47d merged into trunk 5652a1494493; read beside it: mesh-controller 53a3c91f53ce, mesh-controller-main 53a3c91f53ce, mesh-host cd13f7726ef0, mesh-tools 7412c5b6c9c5

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: postgres)
  • mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds postgres, sent nowhere; no bus step; 2 wait(s) for a person

  • tier 0: postgres
  • ace: waits for a person: postgres
  • novox: waits for a person: postgres
  • postgres waits for a person: its policy records (module) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends
  • postgres provides postgres-database: its consumers are sent again after it
  • postgres keeps data (ADR 0233): what it holds is backed up before it moves
  • read by no module's build: modules/postgres/cmd/postgres-provider/published_port_test.go

Run by the build seat on shanks as build-1792181527464265486 (builds --log build-1792181527464265486).

--- the gate: postgres
postgres: ok, keeps state bound, reads mesh-controller.assignments, keeps store (valuable), dumps (rebuildable), ready: server by tcp on database every 30s
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-16T19:55:20Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-16T19:55:20Z

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): postgres

notes:
  - modules/postgres/cmd/postgres-provider/published_port_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.003s
words: 12 retired words and 70 daemons' lines, none in the 53204 strings of 799 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.013s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/mailstore	0.009s
mail-store: claimed only by mesh-mail
ok  	git.novox.be/novox/mesh-catalog/checks/secrets	0.014s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
ok  	git.novox.be/novox/mesh-catalog/checks/predefined	0.258s
predefined.json: 2 key(s), none removed that a module names
ok  	git.novox.be/novox/mesh-catalog/checks/config	0.016s
config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved)
ok  	git.novox.be/novox/mesh-catalog/checks/templates	0.012s
templates: no module keeps a file's text inline but the 0 listed
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 61, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.218s
testing modules/postgres
ok  	postgres/cmd/postgres-provider	1.102s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `deb2020b` Judged: head `deb2020bd47d` merged into trunk `5652a1494493`; read beside it: mesh-controller `53a3c91f53ce`, mesh-controller-main `53a3c91f53ce`, mesh-host `cd13f7726ef0`, mesh-tools `7412c5b6c9c5` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: postgres) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds postgres, sent nowhere; no bus step; 2 wait(s) for a person - tier 0: postgres - ace: waits for a person: postgres - novox: waits for a person: postgres - postgres waits for a person: its policy records (module) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends - postgres provides postgres-database: its consumers are sent again after it - postgres keeps data (ADR 0233): what it holds is backed up before it moves - read by no module's build: modules/postgres/cmd/postgres-provider/published_port_test.go Run by the build seat on shanks as `build-1792181527464265486` (`builds --log build-1792181527464265486`). ``` --- the gate: postgres postgres: ok, keeps state bound, reads mesh-controller.assignments, keeps store (valuable), dumps (rebuildable), ready: server by tcp on database every 30s long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-16T19:55:20Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-16T19:55:20Z machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): postgres notes: - modules/postgres/cmd/postgres-provider/published_port_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.003s words: 12 retired words and 70 daemons' lines, none in the 53204 strings of 799 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/mailstore 0.009s mail-store: claimed only by mesh-mail ok git.novox.be/novox/mesh-catalog/checks/secrets 0.014s secrets: no setting can replace a vault secret in a mergeable file (1 known, nested) ok git.novox.be/novox/mesh-catalog/checks/predefined 0.258s predefined.json: 2 key(s), none removed that a module names ok git.novox.be/novox/mesh-catalog/checks/config 0.016s config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved) ok git.novox.be/novox/mesh-catalog/checks/templates 0.012s templates: no module keeps a file's text inline but the 0 listed ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 61, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.218s testing modules/postgres ok postgres/cmd/postgres-provider 1.102s --- its merge-check-typescript.sh (typescript toolchain) ```
mesh-tools merged commit 017b729bc9 into main 2026-10-16 20:15:34 +00:00
mesh-tools deleted branch fix/957-postgres-serves-published-port 2026-10-16 20:15:34 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
mesh/ready
Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)
No labels mesh/ready
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#339