Take mesh-sdk at 07a6592: an item's text places a config value (issue 1658), and fit the unit level in its bound (issue 1763) #420

Merged

mesh-tools merged 6 commits from fix/1656-xterm-config into main 2026-10-21 18:36:40 +00:00

Conversation 4 Commits 6 Files Changed 8

+14 -9

mesh-tools commented 2026-10-21 13:12:55 +00:00

Member

Copy Link

Copy Source

Delivery group fix/1656-xterm-config with mesh-catalog#416 (issue 1656, xterm's resources as config values).

This member takes mesh-sdk at 07a65927 (mesh-sdk#62, merged and delivered 20:16), which counts an item's text as a placement of a config value (issue 1658), so the catalogue member's template-only config keys are not refused. The SDK change shipped alone before its users (ADR 0482 §7); mesh-sdk#61, the same change inside this group, was closed for #62. Diff against main: go.mod, go.sum, vendor/modules.txt, testdata/beside/CAPTURED line 12, and the vendored catalogue/setting_into.go.

It also carries issue 1763 (the controller's unit level ran at its 5 s bound, failing this member's try and mesh-controller#423 on time): plan_moved_every_writer_test.go runs its costly regexp only on files that can match; sayable_test.go and forge_wait_test.go shorten stand-in waits that no assertion depends on. cmd/mesh-controller unit time 3.52 s -> about 2.2 s; the six changed tests passed 20 times each, with -cpu 1 and under load.

Reviewed-by: reviewer-xterm@shanks at 9d260412b3

Delivery group fix/1656-xterm-config with mesh-catalog#416 (issue 1656, xterm's resources as config values). This member takes mesh-sdk at 07a65927 (mesh-sdk#62, merged and delivered 20:16), which counts an item's text as a placement of a config value (issue 1658), so the catalogue member's template-only config keys are not refused. The SDK change shipped alone before its users (ADR 0482 §7); mesh-sdk#61, the same change inside this group, was closed for #62. Diff against main: go.mod, go.sum, vendor/modules.txt, testdata/beside/CAPTURED line 12, and the vendored catalogue/setting_into.go. It also carries issue 1763 (the controller's unit level ran at its 5 s bound, failing this member's try and mesh-controller#423 on time): plan_moved_every_writer_test.go runs its costly regexp only on files that can match; sayable_test.go and forge_wait_test.go shorten stand-in waits that no assertion depends on. cmd/mesh-controller unit time 3.52 s -> about 2.2 s; the six changed tests passed 20 times each, with -cpu 1 and under load. Reviewed-by: reviewer-xterm@shanks at 9d260412b330053c405ba15b31b3dfb21365808e

mesh-tools commented 2026-10-21 13:13:16 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-controller@9d260412b330 — failed since 2026-10-21T18:59:01Z

Covered: covered after its failure: a later walk that contains it was delivered: plan-1792609673527907956 (novox/mesh-controller at f973cefd into main, done, contains its merge 98155e32)

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

• tier 0: mesh-controller, route-proxy
• tier 1: build-agent
• ace: receives route-proxy, build-agent
• g14: receives build-agent
• novox: receives mesh-controller, route-proxy, build-agent
• shanks: receives build-agent
• 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
• build-agent keeps data (ADR 0233): what it holds is backed up before it moves
• grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before route-proxy, build-agent is judged on its first machine

Group fix/1656-xterm-config: novox/mesh-catalog@b9dcf19c3f, novox/mesh-controller@9d260412b3

• composed together: pass — every machine composes with the change as it did without (4 of 4 compose)

Machines

• mesh-controller on every machine running it: sent
• route-proxy on every machine running it: sent

Transitions

• 2026-10-21 18:00 (new) → proposed (announced): novox/mesh-controller#420's head announced
• 2026-10-21 18:14 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-21 18:14 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-21 18:38 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
• 2026-10-21 18:38 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
• 2026-10-21 18:59 delivering → failed (failed): its walk failed, carrying its own commit: a gate on a first machine (what it carried put back), a build, a machine

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

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-controller@9d260412b330` — **failed** since 2026-10-21T18:59:01Z **Covered**: covered after its failure: a later walk that contains it was delivered: plan-1792609673527907956 (novox/mesh-controller at f973cefd into main, done, contains its merge 98155e32) **Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller, route-proxy - tier 1: build-agent - ace: receives route-proxy, build-agent - g14: receives build-agent - novox: receives mesh-controller, route-proxy, build-agent - shanks: receives build-agent - 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 - build-agent keeps data (ADR 0233): what it holds is backed up before it moves - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before route-proxy, build-agent is judged on its first machine **Group** `fix/1656-xterm-config`: novox/mesh-catalog@b9dcf19c3f91, novox/mesh-controller@9d260412b330 - composed together: pass — every machine composes with the change as it did without (4 of 4 compose) **Machines** - mesh-controller on every machine running it: sent - route-proxy on every machine running it: sent **Transitions** - 2026-10-21 18:00 (new) → proposed (announced): novox/mesh-controller#420's head announced - 2026-10-21 18:14 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-21 18:14 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-21 18:38 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-21 18:38 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-21 18:59 delivering → failed (failed): its walk failed, carrying its own commit: a gate on a first machine (what it carried put back), a build, a machine The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools commented 2026-10-21 14:45:29 +00:00

Author

Member

Copy Link

Copy Source

Merge check at 858b06a9
Judged: head 858b06a94e69 merged into trunk 12752911b644

• mesh/merge-gate: FAIL — head 858b06a94e does not merge cleanly into trunk 12752911b6: in conflict go.mod, go.sum, testdata/beside/CAPTURED, vendor/git.novox.be/novox/mesh-sdk/go/delivery/source.go, vendor/modules.txt
• mesh/repo-check: FAIL — head 858b06a94e does not merge cleanly into trunk 12752911b6: in conflict go.mod, go.sum, testdata/beside/CAPTURED, vendor/git.novox.be/novox/mesh-sdk/go/delivery/source.go, vendor/modules.txt

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

• tier 0: mesh-controller, route-proxy
• tier 1: build-agent
• ace: receives route-proxy, build-agent
• g14: receives build-agent
• novox: receives mesh-controller, route-proxy, build-agent
• shanks: receives build-agent
• 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
• build-agent keeps data (ADR 0233): what it holds is backed up before it moves
• grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before route-proxy, build-agent is judged on its first machine
• read by no module's build: testdata/beside/CAPTURED

Run by the build seat on ace as build-1792593900645662220 (builds --log build-1792593900645662220).

head 858b06a94e69 does not merge cleanly into trunk 12752911b644: in conflict go.mod, go.sum, testdata/beside/CAPTURED, vendor/git.novox.be/novox/mesh-sdk/go/delivery/source.go, vendor/modules.txt

**Merge check** at `858b06a9` Judged: head `858b06a94e69` merged into trunk `12752911b644` - `mesh/merge-gate`: **FAIL** — head 858b06a94e69 does not merge cleanly into trunk 12752911b644: in conflict go.mod, go.sum, testdata/beside/CAPTURED, vendor/git.novox.be/novox/mesh-sdk/go/delivery/source.go, vendor/modules.txt - `mesh/repo-check`: **FAIL** — head 858b06a94e69 does not merge cleanly into trunk 12752911b644: in conflict go.mod, go.sum, testdata/beside/CAPTURED, vendor/git.novox.be/novox/mesh-sdk/go/delivery/source.go, vendor/modules.txt **Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller, route-proxy - tier 1: build-agent - ace: receives route-proxy, build-agent - g14: receives build-agent - novox: receives mesh-controller, route-proxy, build-agent - shanks: receives build-agent - 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 - build-agent keeps data (ADR 0233): what it holds is backed up before it moves - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before route-proxy, build-agent is judged on its first machine - read by no module's build: testdata/beside/CAPTURED Run by the build seat on ace as `build-1792593900645662220` (`builds --log build-1792593900645662220`). ``` head 858b06a94e69 does not merge cleanly into trunk 12752911b644: in conflict go.mod, go.sum, testdata/beside/CAPTURED, vendor/git.novox.be/novox/mesh-sdk/go/delivery/source.go, vendor/modules.txt ```

mesh-tools commented 2026-10-21 14:45:34 +00:00

Author

Member

Copy Link

Copy Source

mesh-delivery: not merged. This pull request's checks passed at 858b06a94e, and now its check failed: head 858b06a94e does not merge cleanly into trunk 12752911b6: in conflict go.mod, go.sum, testdata/beside/CAPTURED, vendor/git.novox.be/novox/mesh-sdk/go/delivery/source.go, vendor/modules.txt (head 858b06a94e merged into trunk 12752911b6). A new head, or a recheck that passes, asks the operator again.

mesh-delivery: **not merged.** This pull request's checks passed at 858b06a94e69d00db974a96ec86cecde3a951da0, and now its check failed: head 858b06a94e69 does not merge cleanly into trunk 12752911b644: in conflict go.mod, go.sum, testdata/beside/CAPTURED, vendor/git.novox.be/novox/mesh-sdk/go/delivery/source.go, vendor/modules.txt (head 858b06a94e69 merged into trunk 12752911b644). A new head, or a recheck that passes, asks the operator again.

mesh-tools commented 2026-10-21 15:02:36 +00:00

Author

Member

Copy Link

Copy Source

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head c8e35097e861 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 c8e35097e861 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.

jschoubben added 1 commit 2026-10-21 15:03:37 +00:00

Take mesh-sdk at 6f63275, which counts an item's text as a placement of a config value (issue 1658) 69a67876c2

jschoubben force-pushed fix/1656-xterm-config from 858b06a94e to 69a67876c2 2026-10-21 15:03:37 +00:00 Compare

mesh-tools changed title from Take mesh-sdk at c8e3509: an item's text places a config value (issue 1658) to Take mesh-sdk at 6f63275: an item's text places a config value (issue 1658) 2026-10-21 15:06:22 +00:00

mesh-tools referenced this pull request from novox/mesh-sdk 2026-10-21 15:21:29 +00:00

Count an item's text as a placement of a config value (issue 1658) #61

mesh-tools referenced this pull request from novox/mesh-sdk 2026-10-21 17:15:19 +00:00

Count an item's text as a placement of a config value (issue 1658) #61

mesh-tools referenced this pull request from novox/mesh-catalog 2026-10-21 17:19:12 +00:00

xterm: every resource a config value, today's values as defaults (issue 1656) #416

jschoubben added 3 commits 2026-10-21 17:43:34 +00:00

Merge origin/main into fix/1656-xterm-config 99da867a98

Merge remote-tracking branch 'origin/main' into fix/1656-xterm-config f66458fe25

Take mesh-sdk at 07a6592, which counts an item's text as a placement of a config value (issue 1658) 373aefd14e

jschoubben added 2 commits 2026-10-21 18:00:16 +00:00

Cut the controller's slowest unit tests (a source scan that regexed every file, resolver stand-in timeouts, a wait bound) so mesh-controller's unit level fits its bound (issue 1763) 99610e9569

Merge remote-tracking branch 'origin/main' into fix/1656-xterm-config 9d260412b3

mesh-tools changed title from Take mesh-sdk at 6f63275: an item's text places a config value (issue 1658) to Take mesh-sdk at 07a6592: an item's text places a config value (issue 1658), and fit the unit level in its bound (issue 1763) 2026-10-21 18:31:34 +00:00

mesh-tools merged commit 98155e327b into main 2026-10-21 18:36:40 +00:00

mesh-tools deleted branch fix/1656-xterm-config 2026-10-21 18:36:40 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

mesh/ready

Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)

No labels

Milestone

No items

No Milestone

Assignees

Clear assignees

agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#420