The manifest's reading of if-config, config-lines and config-json, and a call onto a bundle's own events stream (issue 1979) #190

2026-11-13T01:06:57Z

mesh-tools commented

2026-11-13 01:06:57 +00:00

Issue 1979, design 42 milestone zfs-owns-zfs (§4; lead answers A-13, A-15, A-25, A-41, A-42). Delivery group feature/1979-zfs-owns-zfs with mesh-tools, mesh-host, mesh-delivery and mesh-catalog.

S1 16091228: word:resources.if-config stated and needed.
S2 b54d20ac: forms config-lines and config-json (the exact token ${config-json}, A-25).
f84fe54c: process.Account.BusSubject(local, event), the subject of a module's template events stream (A-41).
2895a21e: buscalls mesh/stream.publish {stream, event, body, id} (A-42).

Quick or thorough: thorough — the stream subject and the publish call are in mesh-sdk for every module, not in zfs alone.

Reviewed-by: mesh-code-reviewer of fix-1977@ace at 2895a21e69

Issue 1979, design 42 milestone zfs-owns-zfs (§4; lead answers A-13, A-15, A-25, A-41, A-42). Delivery group feature/1979-zfs-owns-zfs with mesh-tools, mesh-host, mesh-delivery and mesh-catalog. - S1 16091228: `word:resources.if-config` stated and needed. - S2 b54d20ac: forms `config-lines` and `config-json` (the exact token `${config-json}`, A-25). - f84fe54c: `process.Account.BusSubject(local, event)`, the subject of a module's template events stream (A-41). - 2895a21e: buscalls `mesh/stream.publish` {stream, event, body, id} (A-42). Quick or thorough: thorough — the stream subject and the publish call are in mesh-sdk for every module, not in zfs alone. Reviewed-by: mesh-code-reviewer of fix-1977@ace at 2895a21e69cd8e1fb851fc387e48221815493467

mesh-tools added 4 commits 2026-11-13 01:06:58 +00:00

S1 sdk-if-config-word: the resource key if-config is a reader capability 160912280c

A resource carrying `if-config` needs `word:resources.if-config`, which ManifestReads states.

Builds: design 42 zfs-owns-zfs §4, §2; answer A-13

S2 sdk-config-forms: the forms config-lines and config-json are reader capabilities b54d20ac5a

referenceForms gains config-lines and config-json; textNeeds also finds the exact token ${config-json}, which holds no colon.

Builds: design 42 zfs-owns-zfs §4, §3, §9; answers A-13, A-15, A-24, A-25

mesh-sdk: Account.BusSubject names the subject of a template stream (A-41) f84fe54c6c

Builds: design 42 zfs-owns-zfs A-41

buscalls: StreamPublish says an event on a module's own bound stream (A-42)

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

Details

mesh/delivery-group group feature/1979-zfs-owns-zfs merged: every member is merged

Details

mesh/check being carried to 2895a21e69cd on 8fbba810609e | from e42b9491c931, mesh-catalog 117f933dacf0, mesh-delivery 7221a1e5cd7f, mesh-host 0193949…

2895a21e69

Builds: design 42 zfs-owns-zfs §25, §24, lead answer A-42

mesh-tools commented

2026-11-13 01:07:11 +00:00

Delivery novox/mesh-sdk@2895a21e69cd — merged since 2026-11-13T08:00:31Z

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

Group feature/1979-zfs-owns-zfs: novox/mesh-catalog@0041b69d17, novox/mesh-delivery@ad7e580918, novox/mesh-host@96a8690639, novox/mesh-sdk@2895a21e69, novox/mesh-tools@df2162e381

composed together: pass — the checker's verdict at the members' heads (13bf070ecb87)

Transitions

2026-11-13 01:07 (new) → proposed (announced): novox/mesh-sdk#190's head announced
2026-11-13 01:07 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-13 08:00 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-sdk@2895a21e69cd` — **merged** since 2026-11-13T08:00:31Z **Source** — source.main moved to novox/mesh-sdk@8fbba810609e. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `feature/1979-zfs-owns-zfs`: novox/mesh-catalog@0041b69d1736, novox/mesh-delivery@ad7e58091801, novox/mesh-host@96a869063977, novox/mesh-sdk@2895a21e69cd, novox/mesh-tools@df2162e381f5 - composed together: pass — the checker's verdict at the members' heads (13bf070ecb87) **Transitions** - 2026-11-13 01:07 (new) → proposed (announced): novox/mesh-sdk#190's head announced - 2026-11-13 01:07 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-13 08:00 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 commented

2026-11-13 02:31:30 +00:00

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-tools merged commit 8fbba81060 into main

2026-11-13 08:00:28 +00:00

mesh-tools deleted branch feature/1979-zfs-owns-zfs

2026-11-13 08:00:29 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-sdk#190