-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stuck messages in the timeline #17966
Comments
this is also matrix-org/synapse#9424 (comment) |
I'm slightly worried this is a synapse-side threading issue btw. Mjolnir and such are seeing duplicate events down |
Duplicate of #17471 |
My money is currently on synapse not returning the event in either sync request, to be clear. |
I just got this again and it's worse now because the new 'sent' tick is just on the latest message, so i you send another message afterwards, the latter one can get through but then the two messages just look like they've been re-ordered, and the 'sent' tick is on the one that actually didn't send at all! |
Is anyone aware of a workaround to resolve this. It's quite annoying 😓 |
Have the problem in the matrix HQ chat, too and it's really really anoying |
@ara4n thinks this is an E2EE client bug .. need to understand if that's tracked elsewhere |
This issue also exists in the Android version of the app. @kittykat are you aware of it? |
If I remember correctly it usually happened whenever I had some backlog to sync and I sent the message and closed the app/changed room focus (either or) before backlog did properly sync, which left me with this hanging message. |
New occurence on web for me https://github.com/matrix-org/element-web-rageshakes/issues/10049 |
Closing in favour of more generic element-hq/element-meta#1597 |
Over the last few weeks i've had ~4 instances where a sent message gets stuck at the bottom of the timeline because we didn't successfully receive an echo down /sync. I rageshaked; @richvdh took a look with jaeger and says there may be two competing /sync requests which tried to receive the message, and so it may have fallen between the cracks. As far as I know, eleweb should never be running overlapping sync loops - so it sounds like something is going worryingly wrong here.
The text was updated successfully, but these errors were encountered: