Wait out a resolver that does not answer in a build's registry step, and say it was the resolver (issue 1748) #447

2026-10-23T11:12:46Z

mesh-tools commented

2026-10-23 11:12:46 +00:00

Issue 1748: a build's registry step failed at once when a lookup of the registry's name timed out at the node's resolver (met twice: 2026-10-21 18:33, 2026-10-23 12:59 failing mesh-controller #446's delivery).

waitForRegistry (internal/builder/registry_wait.go) now waits out a failed lookup (failedLookup, from issue 1773) as well as a refused connection, within the existing registryWait bound; both callers (the waiting transport and the push) get it.
Past the bound, the error and the build's log name the resolver, not the registry.
Any other error still fails at once.

Tests: TestABuildWaitsOutAResolverThatDoesNotAnswerAndGoesOn (AC1), TestABuildFailsNamingTheResolverWhenItDoesNotAnswerPastTheBound (AC2), TestAnErrorThatIsNeitherARefusalNorALookupFailsAtOnce (AC3); AC1 and AC2 fail with registry_wait.go at main. Try try-1792753479746151556 passed (unit 1762, integration 3040).

Reviewed-by: review-1748@shanks at 0b312218f9

Issue 1748: a build's registry step failed at once when a lookup of the registry's name timed out at the node's resolver (met twice: 2026-10-21 18:33, 2026-10-23 12:59 failing mesh-controller #446's delivery). - `waitForRegistry` (internal/builder/registry_wait.go) now waits out a failed lookup (`failedLookup`, from issue 1773) as well as a refused connection, within the existing `registryWait` bound; both callers (the waiting transport and the push) get it. - Past the bound, the error and the build's log name the resolver, not the registry. - Any other error still fails at once. Tests: TestABuildWaitsOutAResolverThatDoesNotAnswerAndGoesOn (AC1), TestABuildFailsNamingTheResolverWhenItDoesNotAnswerPastTheBound (AC2), TestAnErrorThatIsNeitherARefusalNorALookupFailsAtOnce (AC3); AC1 and AC2 fail with registry_wait.go at main. Try try-1792753479746151556 passed (unit 1762, integration 3040). Reviewed-by: review-1748@shanks at 0b312218f90fdc208bfc98248c5ec855f58a9921

mesh-tools added 1 commit 2026-10-23 11:12:46 +00:00

Wait out a failed lookup of the registry's name in a build, and say it was the resolver (issue 1748)

mesh/delivery delivered

Details

mesh/check pass 0b312218f90f on c834e4f82137 | unit 1762 run, 0 kept, 4 skipped | integration 3040 run, 0 kept, 16 skipped | over bound: integration (…

0b312218f9

mesh-tools commented

2026-10-23 11:12:55 +00:00

Delivery novox/mesh-controller@0b312218f90f — delivered since 2026-10-23T11:25:46Z

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

Machines

mesh-controller on every machine running it: sent
build-agent on every machine running it: sent

Transitions

2026-10-23 11:12 (new) → proposed (announced): novox/mesh-controller#447's head announced
2026-10-23 11:19 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-23 11:19 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-23 11:20 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 11:20 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-23 11:25 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.

**Delivery** `novox/mesh-controller@0b312218f90f` — **delivered** since 2026-10-23T11:25:46Z **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 **Machines** - mesh-controller on every machine running it: sent - build-agent on every machine running it: sent **Transitions** - 2026-10-23 11:12 (new) → proposed (announced): novox/mesh-controller#447's head announced - 2026-10-23 11:19 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-23 11:19 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-23 11:20 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 11:20 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-23 11:25 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 merged commit 791786d5b8 into main

2026-10-23 11:20:15 +00:00

mesh-tools deleted branch fix/1748-registry-wait-retries-a-lookup

2026-10-23 11:20:16 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#447