element-hq
Stuck message due to failure to correlate /send with /sync
Steps to reproduce
- Sent message
- Message was apparently received
- Didn't get remote echo
- Therefore msg is stuck at the bottom of the timeline
Outcome
What did you expect?
Never to have stuck messages, especially as it could mean that msgs are going missing from /sync responses.
What happened instead?
Stuck msg.
Operating system
No response
Application version
Element version: 1.12.3 Crypto version: Rust SDK 0.14.0 (c3b7918), Vodozemac 0.9.0
How did you install the app?
No response
Homeserver
matrix.org
Will you send logs?
Yes
Never to have stuck messages, especially as it could mean that msgs are going missing from /sync responses.
I should think that's exactly what it means. One for https://github.com/element-hq/synapse, no?
Sorry, having looked properly at the rageshake, it looks to me like the problem is that the remote echo comes back while the initial /send was still in flight, and EW doesn't correct correlate it. It does look like an EW problem.
There is definitely code to handle this, it requires unsigned.transaction_id to be included in the event down /sync I believe though
