Skip to content

supervisor: a chain member after the first joins the walk with no client of its own (chain_expect, #348) - #358

Merged
linuxnow merged 4 commits into
mainfrom
feat/348-chain-expect
Nov 1, 2026
Merged

linuxnow merged 4 commits into
mainfrom
feat/348-chain-expect

Conversation

@linuxnow

@linuxnow linuxnow commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

After a chain's first member, hostd sends the worker chain_expect <instance> <chain> before the add (omx-clap-core 0.26.0, omx-clap-core#442). The worker then puts the plugin in the head's walk with no JACK client of its own, so the order line that follows changes nothing. Before, it opened a client per member and the order line closed it again: on r1, 23 ms per add for the add and 13 ms for the line.

  • A worker that answers chain_expect with -902 (before 0.26.0) gets the add and the order line from then on, as today.
  • An add the worker refuses to put in the chain answers PLACEMENT_INVALID, and nothing of it is left; the controller adds it own.
  • The committed omx-clap-core header is 0.26.0's render, and the contract floor is 0.26.0.

Tests: the fake host answers chain_expect. The daemon tests cover both refusal paths (at the add, and at the order line for a worker without the verb) and the line order the worker gets.

…'s walk (chain_expect), no client of its own (#348)

The worker joins it at its add in the head's client: no JACK client is
opened for it and closed again by the order line. A worker that refuses
chain_expect gets the add and the order line from then on; an add the
worker refuses into the chain answers PLACEMENT_INVALID, nothing of it left.
Needs omx-clap-core's chain_expect (omx-clap-core#441) rendered.
…hat the chain_expect drop path repeats is made unique
…_expect is used only by a worker that answers it
@linuxnow
linuxnow merged commit e0a56a0 into main Nov 1, 2026
26 of 30 checks passed
@linuxnow
linuxnow deleted the feat/348-chain-expect branch November 1, 2026 02:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant