Issue 1889: TestACertificateChainsToTheMeshsOwnAuthority (and every store test) failed 'the identity store did not answer within 20s' under the checker. Cause: the fixtures built the test database's address by cutting the admin address at its last '/', dropping its query (host=), so pgx dialed a default socket where no server is; with every store test waiting 20 s the packages hit go test's 10-minute timeout (only 1271 integration tests ran).
Fix: store.DatabaseForTest(admin, name) keeps the query; used by the identity, inventory and licences fixtures, the template raise and the store live test; identity's fresh uses ForTest. The 20 s readiness bound and its error with the driver's cause are unchanged.
Tests: internal/store/fortest_test.go 1889/AC1 (seen failing first), AC2; unit suite and vet (with and without the integration tag) green. Try try-1792738555268981071 passed: 1749 unit, 3027 integration tests, 337 s (was 601-604 s).
Issue 1889: TestACertificateChainsToTheMeshsOwnAuthority (and every store test) failed 'the identity store did not answer within 20s' under the checker. Cause: the fixtures built the test database's address by cutting the admin address at its last '/', dropping its query (host=<socket dir>), so pgx dialed a default socket where no server is; with every store test waiting 20 s the packages hit go test's 10-minute timeout (only 1271 integration tests ran).
Fix: store.DatabaseForTest(admin, name) keeps the query; used by the identity, inventory and licences fixtures, the template raise and the store live test; identity's fresh uses ForTest. The 20 s readiness bound and its error with the driver's cause are unchanged.
Tests: internal/store/fortest_test.go 1889/AC1 (seen failing first), AC2; unit suite and vet (with and without the integration tag) green. Try try-1792738555268981071 passed: 1749 unit, 3027 integration tests, 337 s (was 601-604 s).
Reviewed-by: review-1889@shanks at 185d0294ebd45c7d868378be4f6153a631f04571
mesh/merge-gate head 185d0294ebd4 merged into trunk 89abce5df955 — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; the ch…
mesh/delivery stopped: a merged change never reached the machines: its walk plan-1792741027874517080 ended done before its word without building build-ag…
The checker's integration store answers on a unix socket named in the query of MESH_TEST_POSTGRES
(?host=<socket dir>&sslmode=disable). The identity, inventory and licences fixtures cut the address at
its last slash and appended ?sslmode=disable, dropping host=, so pgx dialled its default socket where no
server is: every store test waited out its 20 s readiness bound, each package ran into go test's
10-minute timeout, and the verdict named only the first failure,
identity.TestACertificateChainsToTheMeshsOwnAuthority.
store.DatabaseForTest now builds that address for every fixture, keeping the query as the template raise
already did; identity's fresh is ForTest rather than a second copy. The readiness bound and its error,
which wraps the driver's cause, are unchanged.
Deliverynovox/mesh-controller@185d0294ebd4 — stopped since 2026-10-23T08:06:04Z
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
Transitions
2026-10-23 07:06 (new) → proposed (announced): novox/mesh-controller#445's head announced
2026-10-23 07:16 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-23 07:16 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-23 07:26 ready → proposed (trunk moved): out of date: judged against trunk 219fdcd7f0, the trunk is now 89abce5df955; judged again on a recheck or when it is merged
2026-10-23 07:37 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-23 07:37 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-23 07:46 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-23 08:06 published → stopped (stop): a merged change never reached the machines: its walk plan-1792741027874517080 ended done before its word without building build-agent, mesh-controller (moved nothing the mesh holds: nothing to walk), and no later merge into main that contains it delivered them (novox/hq issue 474)
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-controller@185d0294ebd4` — **stopped** since 2026-10-23T08:06:04Z
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
**Transitions**
- 2026-10-23 07:06 (new) → proposed (announced): novox/mesh-controller#445's head announced
- 2026-10-23 07:16 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-23 07:16 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-23 07:26 ready → proposed (trunk moved): out of date: judged against trunk 219fdcd7f00c, the trunk is now 89abce5df955; judged again on a recheck or when it is merged
- 2026-10-23 07:37 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-23 07:37 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-23 07:46 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-23 08:06 published → stopped (stop): a merged change never reached the machines: its walk plan-1792741027874517080 ended done before its word without building build-agent, mesh-controller (moved nothing the mesh holds: nothing to walk), and no later merge into main that contains it delivered them (novox/hq issue 474)
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Merge check at 185d0294
Judged: head 185d0294ebd4 merged into trunk 219fdcd7f00c; read beside it: mesh-catalog 89e15c7bcda6, mesh-controller-main 219fdcd7f00c, mesh-host 48c3e3834c69, mesh-tools e0fadc43d9dd
mesh/merge-gate: PASS — the change touches no module of the mesh's graph
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
read by no module's build: internal/identity/identity_test.go, internal/store/fortest_test.go, internal/store/live_test.go
Run by the build seat on shanks as build-1792739212963618149 (builds --log build-1792739212963618149).
Merge check at 185d0294
Judged: head 185d0294ebd4 merged into trunk 89abce5df955; read beside it: mesh-catalog 89e15c7bcda6, mesh-controller-main 89abce5df955, mesh-host 48c3e3834c69, mesh-tools e0fadc43d9dd
mesh/merge-gate: PASS — the change touches no module of the mesh's graph
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
read by no module's build: internal/identity/identity_test.go, internal/store/fortest_test.go, internal/store/live_test.go
Run by the build seat on shanks as build-1792740399217738433 (builds --log build-1792740399217738433).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Issue 1889: TestACertificateChainsToTheMeshsOwnAuthority (and every store test) failed 'the identity store did not answer within 20s' under the checker. Cause: the fixtures built the test database's address by cutting the admin address at its last '/', dropping its query (host=), so pgx dialed a default socket where no server is; with every store test waiting 20 s the packages hit go test's 10-minute timeout (only 1271 integration tests ran).
Fix: store.DatabaseForTest(admin, name) keeps the query; used by the identity, inventory and licences fixtures, the template raise and the store live test; identity's fresh uses ForTest. The 20 s readiness bound and its error with the driver's cause are unchanged.
Tests: internal/store/fortest_test.go 1889/AC1 (seen failing first), AC2; unit suite and vet (with and without the integration tag) green. Try try-1792738555268981071 passed: 1749 unit, 3027 integration tests, 337 s (was 601-604 s).
Reviewed-by: review-1889@shanks at
185d0294ebDelivery
novox/mesh-controller@185d0294ebd4— stopped since 2026-10-23T08:06:04ZDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Transitions
219fdcd7f0, the trunk is now 89abce5df955; judged again on a recheck or when it is mergedThe commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
185d0294Judged: head
185d0294ebd4merged into trunk219fdcd7f00c; read beside it: mesh-catalog89e15c7bcda6, mesh-controller-main219fdcd7f00c, mesh-host48c3e3834c69, mesh-toolse0fadc43d9ddmesh/merge-gate: PASS — the change touches no module of the mesh's graphmesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1792739212963618149(builds --log build-1792739212963618149).Merge check at
185d0294Judged: head
185d0294ebd4merged into trunk89abce5df955; read beside it: mesh-catalog89e15c7bcda6, mesh-controller-main89abce5df955, mesh-host48c3e3834c69, mesh-toolse0fadc43d9ddmesh/merge-gate: PASS — the change touches no module of the mesh's graphmesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1792740399217738433(builds --log build-1792740399217738433).