A dry-run build is taken in by nothing (hq issue 240) #47

2026-10-05T07:50:20Z

jschoubben commented

2026-10-05 07:50:20 +00:00

build --dry-run asked the builder like any build; the outcome went out on the bus and the daemon recorded and registered it, so an unreviewed branch reached a machine (novox/hq issue 240).

BuildRequest.DryRun, echoed by the builder on BuildResult.DryRun.
build --dry-run sets it.
The daemon's Built sets a dry-run outcome aside: no record, no registration, no plan.

Tests: the daemon takes a dry-run outcome in with no stores at all (anything that tried to record would fail); the mark survives the wire both ways and is absent on an ordinary outcome. go test ./internal/link ./cmd/mesh-builder pass.

The catalogue module also hears mesh-build-machine.built; it records edges only, and a follow-up will make it skip dry-run too.

`build --dry-run` asked the builder like any build; the outcome went out on the bus and the daemon recorded and registered it, so an unreviewed branch reached a machine (novox/hq issue 240). - `BuildRequest.DryRun`, echoed by the builder on `BuildResult.DryRun`. - `build --dry-run` sets it. - The daemon's `Built` sets a dry-run outcome aside: no record, no registration, no plan. Tests: the daemon takes a dry-run outcome in with no stores at all (anything that tried to record would fail); the mark survives the wire both ways and is absent on an ordinary outcome. `go test ./internal/link ./cmd/mesh-builder` pass. The catalogue module also hears `mesh-build-machine.built`; it records edges only, and a follow-up will make it skip `dry-run` too.

jschoubben added 1 commit 2026-10-05 07:50:20 +00:00

Take no dry run in: mark it on the request, echo it on the outcome, set it aside 134d039ff8

A dry run of an unreviewed branch was heard by the daemon like any build, registered, and its
definition reached a machine (novox/hq issue 240). The mark now travels with the build and the
daemon records, registers and plans nothing for it.

jschoubben merged commit 326b1aec14 into main

2026-10-05 09:30:34 +00:00

jschoubben deleted branch fix/a-dry-run-build-is-not-taken-in

2026-10-05 09:30:34 +00:00

mesh-admin commented

2026-10-06 23:09:39 +00:00

Delivery novox/mesh-controller@326b1aec143c — held since 2026-10-06T23:05:28Z

Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.

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

tier 0: mesh-controller
tier 1: build-agent
tier 2: route-proxy
ace: receives build-agent, route-proxy
g14: receives build-agent
novox: receives mesh-controller, build-agent, route-proxy
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
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

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/mesh-controller#47 merged; its head was not heard by this owner, so it is made from the forge's word
2026-10-06 23:05 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

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

**Delivery** `novox/mesh-controller@326b1aec143c` — **held** since 2026-10-06T23:05:28Z Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on. **Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller - tier 1: build-agent - tier 2: route-proxy - ace: receives build-agent, route-proxy - g14: receives build-agent - novox: receives mesh-controller, build-agent, route-proxy - shanks: receives build-agent - build-agent keeps data (ADR 0233): what it holds is backed up before it moves - 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 **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-controller#47 merged; its head was not heard by this owner, so it is made from the forge's word - 2026-10-06 23:05 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 The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

This repo is archived. You cannot comment on pull requests.

2 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#47