Incoming messages can be out-of-order #2
Loading…
Reference in New Issue
Block a user
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?
When receiving many live messages at once (not from a backfill), the messages may get bridged out-of-order.
It seems this happens because each incoming message is handled via a separate IPC call, and no ordering is enforced between IPC calls.
Handling all received messages via a single bulk IPC call might help, but that wouldn't solve ordering issues between multiple bulk calls.
Portals should use some kind of synchronization to ensure that it doesn't bridge received messages out-of-order.
Hopefully fixed by
0ce6b833e3
.