Repository navigation
P5: busbar-transport-stdio leaves for its own repo, pinned (/status row 158) - #901
Open
MattJackson wants to merge 2 commits into
Open
MattJackson wants to merge 2 commits into
MattJackson wants to merge 2 commits into
Conversation
…o; the root pins it (/status row 158) BUSBAR-1.6.0.md l.2220 (#39): "plugin SOURCE never re-enters busbar". l.3962: each plugin crate is pinned back as a git dependency in the root manifest's linked rows. This uses the tcp/http/ws/ store-memory pattern. Crates go 24 -> 23. - crates/busbar-transport-stdio is deleted. GetBusbar/busbar-transport-stdio#14 carries it, byte for byte except the twin layout of lib.rs (the cdylib export is in transport-stdio-plugin), at busbar pin 5c99bef. The root pins that PR's head 604a5caf13 with one git row. The root's edge takes the workspace row, and its `transport-stdio` linked row is unchanged. - deny.toml allow-git gains the repo; plugins.yaml drops pending_crate. Cargo.lock: the package resolves from git, and busbar-contract stays patched to the path crate. - Selftests that planted into the in-tree stdio crate: - linked-dropped-features and plugin-closure-deps scan workspace members only, so their plants move to busbar-transport-webrtc, the one transport still in crates/. - kind-isolation's plants keep their paths: the gate lays every pinned plugin-kind checkout at crates/<package> beneath its overlay (kind_isolation/pinned.rs), as for tcp, http and ws. - Ledgers: - qa/construction.toml drops the manifest-allowlist row for a manifest no longer in crates/, as the ws extraction did. - The census floor `transport = 1` holds: webrtc. - Kept rows, each still measured from the pinned checkout: kind-isolation's stdio cell and root edge, the dep-wall carrier exemption (the crate still resolves) and the audit-ledger scopes (#589 reads pinned plugin scopes from the checkout). - crates/busbar-kernel/Cargo.toml: a comment's example of a self-naming crate is now webrtc. The hit count is unchanged.
This was referenced Oct 14, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
/status row 158: extract
busbar-transport-stdioto its own repo and pin it. Crates go 24 -> 23. Not$.Spec:
It uses the same pattern as tcp, http, ws and store-memory (#783).
Based on predev, not on #561. The only stdio coupling #561 has is two
TransportTailfields insrc/meta.rs(fault_rows,fault_rows_len). #778/#787 carry the same hunk. So #561 needs a stdio pin the same way it already pins tcp, ws, http and grpc (p2-breaker-neutral-ts-pin); it no longer needs an in-tree edit. #561 is a conflicting draft, and stacking this on it would hold row 158 behind it.What
crates/busbar-transport-stdiois deleted. repin: busbar 5c99befcfa; busbar deletes its in-tree stdio crate and pins this repo (P5, row 158) busbar-transport-stdio#14 (CI green) carries it at busbar pin5c99befcfa.lib.rsuses the twin layout: the cdylib export is intransport-stdio-plugin, not behinddropped-in.604a5caf13with one git row.transport-stdiolinked and linked-axes rows are unchanged.deny.toml: allow-git gains the repo.plugins.yaml: dropspending_crate.Cargo.lock: the package resolves from git.busbar-contractstays patched to the path crate.Selftests
linked-dropped-featuresandplugin-closure-depsscan workspace members only. Their plants move from the stdio crate tobusbar-transport-webrtc, the one transport still incrates/.crates/busbar-transport-stdiopaths. The gate lays every pinned plugin-kind checkout atcrates/<package>beneath its overlay (kind_isolation/pinned.rs), as it does for tcp, http and ws.Ledgers
qa/construction.toml's manifest-allowlist row for stdio. It already named deps the manifest no longer had, and the ws extraction removed its row the same way.transport = 1(webrtc still matches it).busbar -> busbar-transport-stdioedge. The mount reads the crate as it read it in-tree;busbar-store-memorykeeps the same rows after P5: extract store-memory to GetBusbar/busbar-store-memory (pinned); plugin-ci builds the release image the conformance suite loads #783.Conflicts (merge-tree against open PRs)
Cargo.toml,Cargo.lockand a modify/delete oncrates/busbar-transport-stdio/src/meta.rs. Its stdio hunk becomes a pin bump to ap2-breaker-neutral-ts-pinbranch of the stdio repo.meta.rs, with the same fix.