Files
orca/src/shared
Neil 482136e352 fix(native-chat): end chat streams that stop delivering instead of leaving them silent (#40691)
A remote chat view could sit on a stream that looked healthy but carried no
frames, so replies never rendered and sends stayed on "Sending…" until the tab
was reopened. Two paths left a stream open after delivery had stopped:

- The host dropped a chat subscriber whose frame failed to send, but never
  ended its stream or logged why. It now logs the failure and ends the stream
  once, so the client resubscribes from its cursor.
- The desktop discards frames from a retired transport generation, but a
  rebuilt control connection advanced the generation without closing the
  streams opened under the old one. Retiring a generation now closes those
  streams, tells their windows (which resubscribe) and logs how many.

The client's reconnect wait now resets only after a stream has stayed up for
10 s, so a host that ends a stream right after its first frames cannot drive a
resubscribe every 750 ms.

Refs #39926
2026-11-10 00:12:08 -08:00
..
…