The indexer learns its own build right at its start, and says when a start takes nothing in (issue 1921) #156

2026-11-05T18:54:15Z

mesh-tools commented

2026-11-05 18:54:15 +00:00

#155's new indexer learnt the old build at its start: FixOwnBuild read the node-engine's runs.fp about one second after systemd started it, while the apply of the new build was still in progress. So its take-in at start found its own held merge naming another build and held it silently (indexer_pending m.00000000000000003162, since 19:34:55).

Own build: the indexer takes the want's build only while its apply is in progress (self, not removed, runs.fp differs, and no attempt names it as failed or held); otherwise runs.fp. ADR 0639 §7 holds: an old process started again while its successor's apply failed or is held keeps its own build.
Said: a start or a hold that decides nothing says so in one journal line, naming the build this process runs and the build the held merges name.
Readable: indexer_pending gives the known own build and since when (tools-are-how-a-module-is-spoken-to).
The flood: "its packages are not read" was said, and the forge asked again, on every recompute for an open pull request's unreadable head. Now only a directory missing from the tree is kept per head, and asked again when the head changes; any other forge failure is asked again and said once per head.

Quick or thorough: quick chosen. The thorough form, the node-engine passing each process the build it starts it with, cannot ship first, since a node-engine merge waits behind the held revision (ADR 0633 §3); it is noted on issue 1921 (note 42).

Delivery: this merge joins #155's held revision, and the newest governs (ADR 0633 §3). The running indexer writes this build's indexer entry, verdict and graph key; the builder builds it and the node-engine starts it, and it takes both merges in at its start. No hand act; this is the live case of issue 1585 and ADR 0633.

Tested: unit and integration levels green in the indexer and takein; no test function added; no manifest changed. Rows fail without each change.

Reviewed-by: mesh-code-reviewer@shanks at e3735da928

https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

#155's new indexer learnt the old build at its start: FixOwnBuild read the node-engine's `runs.fp` about one second after systemd started it, while the apply of the new build was still in progress. So its take-in at start found its own held merge naming another build and held it silently (indexer_pending m.00000000000000003162, since 19:34:55). - **Own build:** the indexer takes the want's build only while its apply is in progress (self, not removed, `runs.fp` differs, and no attempt names it as failed or held); otherwise `runs.fp`. ADR 0639 §7 holds: an old process started again while its successor's apply failed or is held keeps its own build. - **Said:** a start or a hold that decides nothing says so in one journal line, naming the build this process runs and the build the held merges name. - **Readable:** `indexer_pending` gives the known own build and since when (tools-are-how-a-module-is-spoken-to). - **The flood:** "its packages are not read" was said, and the forge asked again, on every recompute for an open pull request's unreadable head. Now only a directory missing from the tree is kept per head, and asked again when the head changes; any other forge failure is asked again and said once per head. Quick or thorough: quick chosen. The thorough form, the node-engine passing each process the build it starts it with, cannot ship first, since a node-engine merge waits behind the held revision (ADR 0633 §3); it is noted on issue 1921 (note 42). Delivery: this merge joins #155's held revision, and the newest governs (ADR 0633 §3). The running indexer writes this build's indexer entry, verdict and graph key; the builder builds it and the node-engine starts it, and it takes both merges in at its start. No hand act; this is the live case of issue 1585 and ADR 0633. Tested: unit and integration levels green in the indexer and takein; no test function added; no manifest changed. Rows fail without each change. Reviewed-by: mesh-code-reviewer@shanks at e3735da928f4b405624478263eef7ccb32ca2f23 https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

mesh-tools added 3 commits 2026-11-05 18:54:15 +00:00

The indexer started during its replacement fixes the successor's build; a start that decides nothing says so; a failing head is said once (issue 1921) 9f9e743b2f

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

A transient forge failure is asked again; only a directory missing from the tree is cached per head (issue 1921) 78d57e1cc6

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

The indexer takes the engine's want as its build only while the apply is in progress (issue 1921)

mesh/check being carried to e3735da928f4 on 8c67adaf9136 | from abe9ea3796ea

mesh/delivery merged: source.main moved to novox/mesh-delivery@8c67adaf9136

Details

e3735da928

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

mesh-tools commented

2026-11-05 18:54:20 +00:00

Delivery novox/mesh-delivery@e3735da928f4 — merged since 2026-11-05T19:22:06Z

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

Transitions

2026-11-05 18:54 (new) → proposed (announced): novox/mesh-delivery#156's head announced
2026-11-05 18:54 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-05 19:22 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@e3735da928f4` — **merged** since 2026-11-05T19:22:06Z **Source** — source.main moved to novox/mesh-delivery@8c67adaf9136. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-05 18:54 (new) → proposed (announced): novox/mesh-delivery#156's head announced - 2026-11-05 18:54 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-05 19:22 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 8c67adaf91 into main

2026-11-05 19:22:04 +00:00

mesh-tools deleted branch fix/1921-own-build-at-start

2026-11-05 19:22:05 +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#156