Issue 1933 (critical): novox has failed every apply since 2026-10-24 00:37. The indexer's done build (key mesh-delivery-indexer.ab105803..., program blob sha256:c163ee4d...) names a blob the artifact store never received, and a plan retry reuses that same done key.
This change is comment-only (the indexer's package comment), chosen by the operator at 01:2x as the recovery: the module directory's tree changes (ca6b5043 -> c5d33c68), so its fingerprint and build key are new and the builder builds and pushes the indexer anew. mesh-controller.plans what-if: builds mesh-delivery-indexer only, sent to novox.
The proper fix of the two faults that let a missing blob reach novox (the builder reuses a done key without asking the store; the controller sends a definition its sweep found missing) follows under issue 1933.
Tests: go test ./... in modules/mesh-delivery-indexer passes (0.8 s); go vet -tags integration ./... clean.
Temporary build -> publish -> deliver mode (issue 1921 note 13): the operator merges by hand.
Reviewed-by: review-1933@shanks at 90a79b1585
Pushed-by: lead-47@shanks
Issue 1933 (critical): novox has failed every apply since 2026-10-24 00:37. The indexer's done build (key mesh-delivery-indexer.ab105803..., program blob sha256:c163ee4d...) names a blob the artifact store never received, and a plan retry reuses that same done key.
This change is comment-only (the indexer's package comment), chosen by the operator at 01:2x as the recovery: the module directory's tree changes (ca6b5043 -> c5d33c68), so its fingerprint and build key are new and the builder builds and pushes the indexer anew. `mesh-controller.plans` what-if: builds mesh-delivery-indexer only, sent to novox.
The proper fix of the two faults that let a missing blob reach novox (the builder reuses a done key without asking the store; the controller sends a definition its sweep found missing) follows under issue 1933.
Tests: `go test ./...` in modules/mesh-delivery-indexer passes (0.8 s); `go vet -tags integration ./...` clean.
Temporary build -> publish -> deliver mode (issue 1921 note 13): the operator merges by hand.
Reviewed-by: review-1933@shanks at 90a79b15854b451fe261bca3794972461c371b05
Pushed-by: lead-47@shanks
Deliverynovox/mesh-delivery@90a79b15854b — delivered since 2026-10-23T23:39:55Z
Delivery plan — builds mesh-delivery-indexer → novox; no bus step
tier 0: mesh-delivery-indexer
novox: receives mesh-delivery-indexer
Machines
mesh-delivery-indexer on every machine running it: sent
Transitions
2026-10-23 23:36 (new) → proposed (announced): novox/mesh-delivery#32's head announced
2026-10-23 23:38 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-23 23:38 held → delivering (release): the operator merged mesh-delivery #32 by hand at 01:38 (23:38:21Z) and said 'merged'; by the operator's 00:24 word (build -> publish -> deliver until checks run again, issue 1921 note 13) their merge is their word to release it; recovery of issue 1933 (novox apply-failing)
2026-10-23 23:39 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-delivery:view -->
**Delivery** `novox/mesh-delivery@90a79b15854b` — **delivered** since 2026-10-23T23:39:55Z
**Delivery plan** — builds mesh-delivery-indexer → novox; no bus step
- tier 0: mesh-delivery-indexer
- novox: receives mesh-delivery-indexer
**Machines**
- mesh-delivery-indexer on every machine running it: sent
**Transitions**
- 2026-10-23 23:36 (new) → proposed (announced): novox/mesh-delivery#32's head announced
- 2026-10-23 23:38 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-23 23:38 held → delivering (release): the operator merged mesh-delivery #32 by hand at 01:38 (23:38:21Z) and said 'merged'; by the operator's 00:24 word (build -> publish -> deliver until checks run again, issue 1921 note 13) their merge is their word to release it; recovery of issue 1933 (novox apply-failing)
- 2026-10-23 23:39 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`.
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 1933 (critical): novox has failed every apply since 2026-10-24 00:37. The indexer's done build (key mesh-delivery-indexer.ab105803..., program blob sha256:c163ee4d...) names a blob the artifact store never received, and a plan retry reuses that same done key.
This change is comment-only (the indexer's package comment), chosen by the operator at 01:2x as the recovery: the module directory's tree changes (
ca6b5043->c5d33c68), so its fingerprint and build key are new and the builder builds and pushes the indexer anew.mesh-controller.planswhat-if: builds mesh-delivery-indexer only, sent to novox.The proper fix of the two faults that let a missing blob reach novox (the builder reuses a done key without asking the store; the controller sends a definition its sweep found missing) follows under issue 1933.
Tests:
go test ./...in modules/mesh-delivery-indexer passes (0.8 s);go vet -tags integration ./...clean.Temporary build -> publish -> deliver mode (issue 1921 note 13): the operator merges by hand.
Reviewed-by: review-1933@shanks at
90a79b1585Pushed-by: lead-47@shanks
Delivery
novox/mesh-delivery@90a79b15854b— delivered since 2026-10-23T23:39:55ZDelivery plan — builds mesh-delivery-indexer → novox; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.