mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-11-19 15:18:40 +01:00
Reverts 4bdda86f. A write timeout can deliver a truncated JSON document: part of the notification is written, the write then fails with TimedOut, and the subscriber, which stays subscribed, reads the prefix followed by the next notification. It also does not bound the stall: nothing evicts the subscriber (each push to it waits another second under the window manager lock), the connect has no timeout (uds_windows offers none), and that Winsock honours SO_SNDTIMEO on AF_UNIX sockets is unverified. The transport change and the Windows connect closure are both reverted, including the skip-on-timeout test (the connect parameter of notify_sockets was already there and is unchanged). Follow-up, not done: an eviction policy for a subscriber that does not take a notification, together with a timeout that was verified on Windows (or a non-blocking write with a per-subscriber queue). Decision D-coord-10. Behaviour is back to cand4's predecessor (no timeout). Verified: tools/fast-check (native, Windows clippy -D warnings) PASS; e2e not needed beyond commands.