Skip to content

Serve the container IPC bridge on every host - #134

Merged
lexoliu merged 1 commit into
devfrom
fix/133-windows-ipc-bridge
Oct 15, 2026
Merged

lexoliu merged 1 commit into
devfrom
fix/133-windows-ipc-bridge

Conversation

@lexoliu

@lexoliu lexoliu commented Oct 15, 2026

Copy link
Copy Markdown
Owner

start_container_ipc_bridge and its connection loop were compiled only under cfg(unix), with a stub that always returned container IPC bridge is only supported on unix hosts. The bridge is a std::net TCP listener driven by async-io speaking the TCP IPC message format — no unix sockets or fd passing — so the gates and the stub are removed and one implementation serves every host.

New test container_ipc_bridge_round_trips_a_command_over_tcp (no cfg gate) starts the bridge on loopback, sends one IPC command over TCP and checks the exact response; the windows-latest portability job runs it. macOS: fmt, clippy -D warnings, aither-sandbox 165 tests pass.

Closes #133

The bridge is a std TCP listener driven by async-io and speaks the TCP
IPC message format; nothing in it depends on unix, yet it was compiled
only under cfg(unix) with a stub that always failed elsewhere, so a
container session on a Windows host could run no IPC command. The gates
and the stub are gone, and a host-side round-trip test runs on every
platform.

Closes #133
@codecov-commenter

Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@lexoliu
lexoliu merged commit 7648348 into dev Oct 15, 2026
15 checks passed
This was referenced Oct 15, 2026
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.

Container IPC bridge is unavailable on Windows hosts

2 participants