The tool runner publishes a bundle's event onto its own bound events stream (issue 1979) #70

Merged
mesh-tools merged 2 commits from feature/1979-zfs-owns-zfs into main 2026-11-13 08:00:54 +00:00
Member

Issue 1979, design 42 milestone zfs-owns-zfs (lead answers A-42, A-44). Delivery group feature/1979-zfs-owns-zfs with mesh-sdk, mesh-host, mesh-delivery and mesh-catalog.

  • a775b42e: the tool runner answers mesh/stream.publish for the calling bundle's own bound stream only (another module's or a non-stream binding refused), an acknowledged JetStream publish on the binding's subject plus .<event>, the id as the message id, under the grant the runner already holds (boundOf).
  • df2162e3: the call is the family of its own capability stream-publish, stated by the runner, so a module asking for it is placed only where the runner answers it (A-44).

Quick or thorough: thorough — a bundle had no way onto a template events stream (met twice: the zfs keeper, the zfs tools; messenger shows the same gap, noted on issue 1979).

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

Issue 1979, design 42 milestone zfs-owns-zfs (lead answers A-42, A-44). Delivery group feature/1979-zfs-owns-zfs with mesh-sdk, mesh-host, mesh-delivery and mesh-catalog. - a775b42e: the tool runner answers `mesh/stream.publish` for the calling bundle's own bound stream only (another module's or a non-stream binding refused), an acknowledged JetStream publish on the binding's subject plus `.<event>`, the id as the message id, under the grant the runner already holds (`boundOf`). - df2162e3: the call is the family of its own capability `stream-publish`, stated by the runner, so a module asking for it is placed only where the runner answers it (A-44). Quick or thorough: thorough — a bundle had no way onto a template events stream (met twice: the zfs keeper, the zfs tools; messenger shows the same gap, noted on issue 1979). Reviewed-by: mesh-code-reviewer of fix-1977@ace at df2162e381f5c192884e81dbb49de782ac6ca9da
mesh-tools added 2 commits 2026-11-13 01:06:58 +00:00
Builds: design 42 zfs-owns-zfs §25, §24, lead answer A-42
tool runner: mesh/stream.publish is the capability stream-publish, taken out of bus-state-calls (A-44)
mesh/delivery merged: source.main moved to novox/mesh-tools@af8385495688
mesh/delivery-group group feature/1979-zfs-owns-zfs merged: every member is merged
mesh/check being carried to df2162e381f5 on af8385495688 | from 447a8d035935, mesh-catalog 117f933dacf0, mesh-delivery 7221a1e5cd7f, mesh-host 0193949…
df2162e381
Builds: design 42 zfs-owns-zfs §25, lead answer A-44
Author
Member

Delivery novox/mesh-tools@df2162e381f5 — merged since 2026-11-13T08:00:55Z

Source — source.main moved to novox/mesh-tools@af83854956. 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-tools#70'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-delivery:view --> **Delivery** `novox/mesh-tools@df2162e381f5` — **merged** since 2026-11-13T08:00:55Z **Source** — source.main moved to novox/mesh-tools@af8385495688. 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-tools#70'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`.
Author
Member

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-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 af83854956 into main 2026-11-13 08:00:54 +00:00
mesh-tools deleted branch feature/1979-zfs-owns-zfs 2026-11-13 08:00:55 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-tools#70