Messages sent after a conversation reset or a cancelled request are no longer silently dropped.
What's wrong with this entry?
Two index bugs in the input-stream loop are fixed, so messages after a reset or a cancelled request are not silently dropped.
- The read index is reset whenever a
conversation_resetevent appears in the pending batch, instead of only when a filtered condition held. - When a cancelled request's placeholder text message is spliced out, the read index is decremented if it sat past the removal point.
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
The stdin transport now answers the remote-transport questions
Both mention transport
-
v2.1.248
Undelivered events can be handed to a replacement connection
Both mention transport
-
v2.1.248
Stalled WebSocket sends are now detected instead of hanging
Both mention transport