Eric Traut 79ea577156 TUI: Keep remote app-server events draining (#18932) ...

Addresses #18860

Problem: Remote app-server clients could stop draining websocket events
when their bounded local event channel filled, leaving clients stuck on
stale in-progress turns after a disconnect.

Solution: Use an unbounded local event channel for the remote client so
the websocket reader can keep forwarding disconnect and progress events
instead of blocking or dropping them.

Why this is reasonable: This does not make the remote websocket itself
unbounded. The changed queue lives inside the remote client, between the
task that reads the remote websocket and the API consumer in the same
client process. Once an event has been received from the remote server,
preserving it is preferable to blocking websocket reads or dropping
disconnect/lifecycle events; network-level backpressure still happens at
the websocket boundary if the remote side outpaces the client.

2026-04-22 09:29:34 -07:00

..

lib.rs

Support multiple managed environments (#18401)

2026-04-21 15:29:35 -07:00

remote.rs

TUI: Keep remote app-server events draining (#18932)

2026-04-22 09:29:34 -07:00