Forward with a comment arrives out of order #13
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
build: anotherim-js 0.7.18, libtacky 1.1.18
Several messages forwarded to a room with a comment arrive in the wrong order for other members.
expected: the forwarded messages appear first, in their original order, followed by the comment
actual: The last forwarded message comes first, then the comment as a separate message, then the rest of the forwarded messages in order
In an encrypted room the first sends of a batch wait for keys; a message made after the keys arrived went out at once, ahead of the ones still waiting, so the last forward came first. Since libtacky 1.1.19 (app 0.8.0-beta1 and later) every message to a chat leaves in the order it was made. 1.2.0-rc2 adds a test for exactly this case: a comment plus three forwards into an encrypted room with keys arriving mid-batch.
The comment goes first and the forwards follow in their original order, as in Telegram; that order is by design.