disk-load builds on the current mesh-sdk, so it accepts nats manifest again (issue 1952) #583

2026-10-31T22:03:08Z

mesh-tools commented

2026-10-31 22:03:08 +00:00

disk-load builds on the current mesh-sdk (5ae69df8), so disk-load accepts nats's manifest again. Issue 1952 (design 47 L4: health leaves the controller).

Why. Since 2026-10-30 disk-load on every machine refused each round: "nats's tools bundle tools's bus removes "ASSIGNMENTS", which is not one of DEAD_LETTER_NOTICES.controller, mesh-host_acts (novox/hq ADR 0564 Limits 4)". Its mesh-sdk copy (2da0de75) predates RemovesAssignmentsStream (go/catalogue/process_bus.go). No machine was measured, novox kept no readings, and the controller's stale data-quiet on novox's jetstream keeps mesh-conditions.compare apart, which refuses the L4 take-over.

Quick or thorough. Quick (this): move the pin, as mesh-catalog #580 did for mesh-build-go. It is a hand-set version against ADR 0573 §2, a recovery only, said to and approved by the operator (Telegram 23:02). Thorough: issue 1585 (every module on the latest published mesh-sdk), with a note to judge a manifest once where it enters (the indexer and the merge check) and let readers take only what they need, never refusing a whole read for one manifest.

Checked. Both modules build, vet (also -tags integration), unit tests, go mod verify, go mod tidy -diff; catalogue checks deps and locks. The reviewer proved with catalogue.ParseManifestForInputs on modules/nats/module.json: refused at 2da0de75, accepted at 5ae69df8; no behaviour change in what either module uses. artifact-store-tools was bumped at first and is back as on main (7e5980ff): it does not need it, and its check failed on TestTheSeatSweepsAtABuildsEndOnARealBusOnceTheLeaseIsAway, which fails the same way at main's pin (reproduced locally; noted on issue 1955).

Delivered when disk-load runs the new build on all four machines and novox has readings again (disk-load.disk_readings); then compare loses machine.novox.nats.jetstream.data-quiet.

Tools: no new behaviour, so no new tool; readings are read by disk-load.disk_readings.

Reviewed-by: rev-diskload@shanks at 7e5980ff17

https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

disk-load builds on the current mesh-sdk (5ae69df8), so disk-load accepts nats's manifest again. Issue 1952 (design 47 L4: health leaves the controller). **Why.** Since 2026-10-30 disk-load on every machine refused each round: "nats's tools bundle tools's bus removes "ASSIGNMENTS", which is not one of DEAD_LETTER_NOTICES.controller, mesh-host_acts (novox/hq ADR 0564 Limits 4)". Its mesh-sdk copy (2da0de75) predates `RemovesAssignmentsStream` (go/catalogue/process_bus.go). No machine was measured, novox kept no readings, and the controller's stale data-quiet on novox's jetstream keeps `mesh-conditions.compare` apart, which refuses the L4 take-over. **Quick or thorough.** Quick (this): move the pin, as mesh-catalog #580 did for mesh-build-go. It is a hand-set version against ADR 0573 §2, a recovery only, said to and approved by the operator (Telegram 23:02). Thorough: issue 1585 (every module on the latest published mesh-sdk), with a note to judge a manifest once where it enters (the indexer and the merge check) and let readers take only what they need, never refusing a whole read for one manifest. **Checked.** Both modules build, vet (also `-tags integration`), unit tests, `go mod verify`, `go mod tidy -diff`; catalogue checks deps and locks. The reviewer proved with `catalogue.ParseManifestForInputs` on modules/nats/module.json: refused at 2da0de75, accepted at 5ae69df8; no behaviour change in what either module uses. artifact-store-tools was bumped at first and is back as on main (7e5980ff): it does not need it, and its check failed on TestTheSeatSweepsAtABuildsEndOnARealBusOnceTheLeaseIsAway, which fails the same way at main's pin (reproduced locally; noted on issue 1955). **Delivered when** disk-load runs the new build on all four machines and novox has readings again (disk-load.disk_readings); then compare loses machine.novox.nats.jetstream.data-quiet. Tools: no new behaviour, so no new tool; readings are read by `disk-load.disk_readings`. Reviewed-by: rev-diskload@shanks at 7e5980ff17e092735edefb53a712370926bd4fe8 https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

mesh-tools added 1 commit 2026-10-31 22:03:09 +00:00

disk-load and artifact-store-tools build on the current mesh-sdk, so they accept nats's manifest again (issue 1952)

mesh/delivery closed: a newer head of the same pull request

Details

mesh/check failed: integration: artifactstoretools/cmd/artifact-store-tools.TestTheSeatSweepsAtABuildsEndOnARealBusOnceTheLeaseIsAway: the hand acts r…

654d90a211

Since 2026-10-30 disk-load on every machine refused each round ("nats's tools bundle tools's bus removes
"ASSIGNMENTS", which is not one of ..."): its mesh-sdk copy (2da0de75) predates the allowance for removing
the ASSIGNMENTS stream (process_bus.go RemovesAssignmentsStream). No machine was measured, novox kept no
readings, and the controller's stale data-quiet on novox's jetstream kept mesh-conditions.compare apart,
refusing the L4 take-over. artifact-store-tools composes from the bus on the same copy and gets the same
pin. Same kind as mesh-catalog #580 for mesh-build-go; the thorough fix (every module on the latest
published mesh-sdk) is issue 1585.

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

mesh-tools commented

2026-10-31 22:03:12 +00:00

Delivery novox/mesh-catalog@7e5980ff17e0 — merged since 2026-10-31T22:18:29Z

Source — source.main moved to novox/mesh-catalog@444c2903af. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Transitions

2026-10-31 22:11 (new) → proposed (announced): novox/mesh-catalog#583's head announced
2026-10-31 22:11 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-10-31 22:18 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/mesh-catalog@7e5980ff17e0` — **merged** since 2026-10-31T22:18:29Z **Source** — source.main moved to novox/mesh-catalog@444c2903af7b. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-10-31 22:11 (new) → proposed (announced): novox/mesh-catalog#583's head announced - 2026-10-31 22:11 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-10-31 22:18 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

jschoubben added 1 commit 2026-10-31 22:11:37 +00:00

artifact-store-tools keeps its pin: it does not read other modules' manifests, and its sweep test fails on main as well (issue 1955)

mesh/delivery merged: source.main moved to novox/mesh-catalog@444c2903af7b

Details

mesh/check being carried to 7e5980ff17e0 on 444c2903af7b | from 19714898986c

7e5980ff17

The check on 654d90a2 failed on TestTheSeatSweepsAtABuildsEndOnARealBusOnceTheLeaseIsAway, which fails the same
way at main's pin (2 hand acts recorded where 3 are expected; reproduced locally in 0.1 s). Not this change's.

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

mesh-tools commented

2026-10-31 22:11:40 +00:00

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head 654d90a211 is no longer the pull request's head, or the pull request closed. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head 654d90a21198 is no longer the pull request's head, or the pull request closed. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-tools merged commit 444c2903af into main

2026-10-31 22:18:27 +00:00

mesh-tools deleted branch fix/disk-load-sdk

2026-10-31 22:18:27 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#583