Give route-proxy a new build: the controller's sweep removed its last build's files from the store, so novox and ace cannot apply (issue 1933) #450

2026-10-24T00:37:54Z

mesh-tools commented

2026-10-24 00:37:54 +00:00

Issue 1933 (critical, met a second time): since 01:58 novox and ace fail every apply on route-proxy.bundle-provider (sha256:f1c8a99b... answers 404). The controller's own sweep let go of the 01:52 build's archives seconds after taking the build in (note 7); a retry sends the same build again.

This change is comment-only (route-provider's package comment), the operator's choice at 02:2x for recovery: route-proxy's fingerprint changes, so it is built and pushed anew. What-if: builds mesh-controller (repo-wide source, no code change) and route-proxy (ace first, then the rest). Risk: until the controller fix (branch fix/1933-sweep-keeps-fresh-builds, in progress) is delivered, the same sweep can remove this build too; the sweep logs it within a minute.

Tests: go test ./... in modules/route-proxy passes (1.1 s); go vet -tags integration ./... clean; go build ./... at the root.

Temporary build -> publish -> deliver mode (issue 1921 note 13): the operator merges by hand.

Reviewed-by: review-1933rp@shanks at f13d42abb4
Pushed-by: lead-47@shanks

Issue 1933 (critical, met a second time): since 01:58 novox and ace fail every apply on route-proxy.bundle-provider (sha256:f1c8a99b... answers 404). The controller's own sweep let go of the 01:52 build's archives seconds after taking the build in (note 7); a retry sends the same build again. This change is comment-only (route-provider's package comment), the operator's choice at 02:2x for recovery: route-proxy's fingerprint changes, so it is built and pushed anew. What-if: builds mesh-controller (repo-wide source, no code change) and route-proxy (ace first, then the rest). Risk: until the controller fix (branch fix/1933-sweep-keeps-fresh-builds, in progress) is delivered, the same sweep can remove this build too; the sweep logs it within a minute. Tests: `go test ./...` in modules/route-proxy passes (1.1 s); `go vet -tags integration ./...` clean; `go build ./...` at the root. Temporary build -> publish -> deliver mode (issue 1921 note 13): the operator merges by hand. Reviewed-by: review-1933rp@shanks at f13d42abb4623b88a87a87228f26c34fe5d320d0 Pushed-by: lead-47@shanks

mesh-tools added 1 commit 2026-10-24 00:37:54 +00:00

Give route-proxy a new build: the controller's sweep removed its last build's files from the store, so novox and ace cannot apply (issue 1933)

mesh/delivery delivered

Details

f13d42abb4

mesh-tools commented

2026-10-24 00:38:00 +00:00

Delivery novox/mesh-controller@f13d42abb462 — delivered since 2026-10-24T00:43:52Z

Delivery plan — builds mesh-controller, route-proxy → ace, novox; no bus step

tier 0: mesh-controller, route-proxy
ace: receives route-proxy
novox: receives mesh-controller, route-proxy
route-proxy provides route: its consumers are sent again after it
route-proxy 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 route-proxy is judged on its first machine

Machines

mesh-controller on every machine running it: sent
route-proxy on every machine running it: sent

Transitions

2026-10-24 00:37 (new) → proposed (announced): novox/mesh-controller#450's head announced
2026-10-24 00:39 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
2026-10-24 00:39 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's plans go
2026-10-24 00:43 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@f13d42abb462` — **delivered** since 2026-10-24T00:43:52Z **Delivery plan** — builds mesh-controller, route-proxy → ace, novox; no bus step - tier 0: mesh-controller, route-proxy - ace: receives route-proxy - novox: receives mesh-controller, route-proxy - route-proxy provides route: its consumers are sent again after it - route-proxy 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 route-proxy is judged on its first machine **Machines** - mesh-controller on every machine running it: sent - route-proxy on every machine running it: sent **Transitions** - 2026-10-24 00:37 (new) → proposed (announced): novox/mesh-controller#450's head announced - 2026-10-24 00:39 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on - 2026-10-24 00:39 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's `plans go` - 2026-10-24 00:43 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`.

jschoubben merged commit fa734d3098 into main

2026-10-24 00:39:47 +00:00

jschoubben deleted branch fix/1933-rebuild-route-proxy

2026-10-24 00:39:48 +00:00

jschoubben referenced this issue from a commit

2026-10-24 00:49:57 +00:00

Give route-proxy a build the fixed controller takes in, dropping the incident note #450 added (issue 1933)

mesh-tools referenced this pull request

2026-10-24 00:57:15 +00:00

Give route-proxy a build the fixed controller takes in, dropping the incident note #450 added (issue 1933) #452

jschoubben referenced this issue from a commit

2026-10-24 01:00:19 +00:00