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

2026-10-24T00:57:15Z

mesh-tools commented

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

Issue 1933: route-proxy's builds of 01:52 and 02:43 lost their files to the controller's sweep (fixed by #451), so novox and ace fail every apply on route-proxy.bundle-provider. This comment-only change drops the paragraph #450 added and rewords one line, so route-proxy's directory tree is new (f3c0da02; it was 592fdeb0 at fdf26a1f and b9cf17bc at fa734d30, both builds whose files are gone): the builder builds it anew, and the fixed controller holds every file before it takes the build in.

Merge only after #451's delivery is done.

Tests: go test ./... and go vet -tags integration ./... in modules/route-proxy; go build ./... at the root; gofmt clean.

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

Reviewed-by: review-1933rp2@shanks at 899389c710
Pushed-by: lead-47@shanks

Issue 1933: route-proxy's builds of 01:52 and 02:43 lost their files to the controller's sweep (fixed by #451), so novox and ace fail every apply on route-proxy.bundle-provider. This comment-only change drops the paragraph #450 added and rewords one line, so route-proxy's directory tree is new (f3c0da02; it was 592fdeb0 at fdf26a1f and b9cf17bc at fa734d30, both builds whose files are gone): the builder builds it anew, and the fixed controller holds every file before it takes the build in. Merge only after #451's delivery is done. Tests: `go test ./...` and `go vet -tags integration ./...` in modules/route-proxy; `go build ./...` at the root; gofmt clean. Temporary build -> publish -> deliver mode (issue 1921 note 13): the operator merges by hand. Reviewed-by: review-1933rp2@shanks at 899389c7106c41c0d9c8c5455172f2734f81552b Pushed-by: lead-47@shanks

mesh-tools added 2 commits 2026-10-24 00:57:16 +00:00

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

Reword route-provider's stdout line, so route-proxy's tree differs from the 01:52 build whose files are gone (issue 1933)

mesh/delivery delivered

Details

899389c710

mesh-tools commented

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

Delivery novox/mesh-controller@899389c7106c — delivered since 2026-10-24T01:06:08Z

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:57 (new) → proposed (announced): novox/mesh-controller#452's head announced
2026-10-24 01:00 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 01:00 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 01:06 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@899389c7106c` — **delivered** since 2026-10-24T01:06:08Z **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:57 (new) → proposed (announced): novox/mesh-controller#452's head announced - 2026-10-24 01:00 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 01:00 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 01:06 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 1c50608246 into main

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

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

2026-10-24 01:00:19 +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#452