Skip to content

supervisor: add into a chain's worker, no worker of its own and no move (#348) - #357

Merged
linuxnow merged 3 commits into
mainfrom
feat/348-add-into-chain
Oct 31, 2026
Merged

linuxnow merged 3 commits into
mainfrom
feat/348-add-into-chain

Conversation

@linuxnow

Copy link
Copy Markdown
Contributor

Builds point 1 and 2 of #348: add <uri> <inst> chain:<n>. The settled questions are in the issue body.

Tests, red first: the two new daemon tests failed on main (chain:7 was read as a client name) and pass here. The fake host gains FAKE_REFUSE_CHAIN_MEMBER. make -k test passes in the worker image.

The add-time bench row follows in the release PR.

…'s worker (#348)

The add goes into the chain's worker at the end of the chain: no worker of
its own and no move. The first add of a chain opens its worker; each add
sends the worker the order with the new member. A member the worker refuses
to run in the chain is removed and the add answers PLACEMENT_INVALID, so the
caller adds it own. The add is refused the same way for a planned chain, a
chain whose worker is not up, a quarantined plugin and, under require_pins, a
format whose pin holds only in a world of its own.
…worker per plugin (#348)

H2 chain-add adds each plugin with add <uri> <id> chain:1 and times it until
the chain runs, as the chain mode is timed. A daemon before #348 gives the
row unsupported.
@linuxnow
linuxnow merged commit d987b3a into main Oct 31, 2026
34 checks passed
@linuxnow
linuxnow deleted the feat/348-add-into-chain branch October 31, 2026 20:34
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