The delivery view names a lagging node's builds by fingerprint and what moved, and says a failed build as failed (issue 1966) #194

2026-11-09T22:00:04Z

mesh-tools commented

2026-11-09 22:00:04 +00:00

mesh-delivery.deliveries said, for about 20 merges, "runs the build of 05e21fd8, not yet that of 05e21fd8": the same source commit twice, where the builds differ by fingerprint (a moved mesh package). The reach line now names each build's fingerprint with its commit, and when the commit is the same, what moved (the tree, a lock, a base module, the builder, or a mesh package by name). A build that failed is said as failed with the first words of its error: "its newest build" only when it is the newest, otherwise "the build it waits for". Rows are cases of TestTheViewDerivesHowFarEachRepositoryReached.

Not built: the version a moved mesh package resolved to (the indexer keeps only the names).

issue 1966

Reviewed-by: review-1966@shanks at 85cf4712fc
Pushed-by: lead-47@shanks

https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

mesh-delivery.deliveries said, for about 20 merges, "runs the build of 05e21fd8, not yet that of 05e21fd8": the same source commit twice, where the builds differ by fingerprint (a moved mesh package). The reach line now names each build's fingerprint with its commit, and when the commit is the same, what moved (the tree, a lock, a base module, the builder, or a mesh package by name). A build that failed is said as failed with the first words of its error: "its newest build" only when it is the newest, otherwise "the build it waits for". Rows are cases of TestTheViewDerivesHowFarEachRepositoryReached. Not built: the version a moved mesh package resolved to (the indexer keeps only the names). issue 1966 Reviewed-by: review-1966@shanks at 85cf4712fc595eb1d98ec1b841c1ce6ffc22a4a2 Pushed-by: lead-47@shanks https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

mesh-tools added 2 commits 2026-11-09 22:00:04 +00:00

The view says a lagging node's build by fingerprint, what moved, and a failed newest build (issue 1966) 47026d5ebb

The hold named the same commit twice when only a mesh package moved. It now names both builds
by fingerprint with their commits, the input that moved when the commit is the same, and says a
newest build that failed as failed with its first words.

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

Put the lagging-build rows into the existing reach test, and word a build that is not the newest as the build the node waits for (issue 1966)

mesh/delivery merged: source.main moved to novox/mesh-delivery@1e21adfde221

Details

mesh/check checking 85cf4712fc59 on 10066c5ec0c0

85cf4712fc

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

mesh-tools commented

2026-11-09 22:00:09 +00:00

Delivery novox/mesh-delivery@85cf4712fc59 — merged since 2026-11-09T22:08:23Z

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

Transitions

2026-11-09 22:00 (new) → proposed (announced): novox/mesh-delivery#194's head announced
2026-11-09 22:00 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-11-09 22:08 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-delivery@85cf4712fc59` — **merged** since 2026-11-09T22:08:23Z **Source** — source.main moved to novox/mesh-delivery@1e21adfde221. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-09 22:00 (new) → proposed (announced): novox/mesh-delivery#194's head announced - 2026-11-09 22:00 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-11-09 22:08 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`.

mesh-tools merged commit 1e21adfde2 into main

2026-11-09 22:08:22 +00:00

mesh-tools deleted branch fix/1966-view-names-builds

2026-11-09 22:08:22 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-delivery#194