Under the hood
Useful2 Signal2
A conversation reset can no longer be discarded when the event queue is overloaded.
What's wrong with this entry?
Anonymous. No account, no email.
What
When the bounded queue of task events fills up, it no longer evicts a conversation reset. Resets and null-status system frames are skipped as eviction candidates and the next eligible entry is evicted instead, so a reset cannot be lost under load.
Details
- Tearing down the remote-control bridge while a reset is still undelivered now reports that fact and resets the bridge's own state.
Evidence
bridge_conversation_reset
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Remote bridge replaces stale-epoch recovery with a one-shot supersession close
Both mention bridge
-
v2.1.236
Remote bridge waits for the disconnect notice, and an inbox fetch that is always off
Both mention bridge
-
v2.1.236
Bridge shuts down cleanly on SIGHUP
Both mention bridge