Skip to content

fix: use blocking sockets for daemon connections - #1

Merged
jlongster merged 1 commit into
masterfrom
macos-subscriptions
Aug 26, 2026
Merged

jlongster merged 1 commit into
masterfrom
macos-subscriptions

Conversation

@jlongster

Copy link
Copy Markdown
Collaborator

Summary

  • Explicitly set accepted Unix sockets to blocking mode. On macOS they inherit the nonblocking listener mode, causing the subscription disconnect monitor to treat WouldBlock as a disconnected client.
  • Extend the existing streaming test to verify delayed live output as well as initial replay.

Verification

  • Reproduced streaming test failure on macOS before the fix; it passes after the fix.
  • cargo test: all 13 tests pass.
  • cargo fmt --check and cargo clippy --all-targets --all-features -- -D warnings pass.
  • OpenCode server integration now exchanges input/output through both attachments, but still fails its separate foreground-process metadata assertion (both values remain null).

No OpenCode production build or protocol changes are required.

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