l0ng-ai fc01b3e31f fix(client): stop timeout setup from masking the daemon's refusal ...

On macOS, setsockopt against a socket whose peer has already closed fails with
EINVAL. The daemon answers a bad request by writing one Error frame and hanging
up at once, so PaneSession's `set_recv_timeout(...)?` would fail before the
refusal was ever read — turning "no such pane 42", already sitting in the
buffer, into "Invalid argument".

Bounding the reply wait is an optimisation, not a correctness requirement, so it
is now best effort in both attach/observe and spawn. Nothing can hang as a
result: a closed peer returns EOF immediately, and a live peer is exactly the
case where setsockopt succeeds.

This is what made client_lib's reattach test red.

2026-07-31 13:04:51 +08:00

..

cli.rs

chore: strip every comment from the Rust sources (#268)

2026-07-30 21:36:15 +08:00

client_lib.rs

fix(client): stop timeout setup from masking the daemon's refusal

2026-07-31 13:04:51 +08:00

machine_tree.rs

chore: strip every comment from the Rust sources (#268)

2026-07-30 21:36:15 +08:00

pane_send_input.rs

fix(daemon): wake displaced controllers without polling, keep busy links usable

2026-07-31 13:04:33 +08:00

remote_router.rs

chore: strip every comment from the Rust sources (#268)

2026-07-30 21:36:15 +08:00

routed_pane.rs

feat(core): pane observers, TTY7_* context env, and control aggregate queries

2026-07-31 09:44:22 +08:00

stdio_conformance.rs

chore: strip every comment from the Rust sources (#268)

2026-07-30 21:36:15 +08:00