-
Notifications
You must be signed in to change notification settings - Fork 730
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
Quick Work around to remove stuck messages #3004
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just one small remark. Also, any idea of the root cause?
actionPermissions: ActionPermissions, | ||
messageContent: MessageContent?, | ||
msgType: String?) { | ||
if (timelineEvent.root.sendState == SendState.SENT) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test is already done before calling this method, so we could remove it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Root cause is complex and hard to catch on synapse side, two main scenario could cause that:
- It could be the downstream bug (Missing event down /sync for some devices, but not others matrix-org/synapse#9624)
- Or a gappy sync scenario (two much events, and the synced event is in the gap, and in this case clients should have some mechanism to backfill if a sent event is not synced after following sync...)
Never mind, I did not see the link to Synapse issues. Thanks |
(Please fix the warning in the code) |
Quick work around to remove stuck messages at the bottom of timeline.
Currently only choice is to clear cache and do a full initial sync.
This PR is just adding an option to cancel sent but not synced message, only effect is that it will delete the local echo.
This does not fix the root issues, See:
#516
matrix-org/synapse#9424
matrix-org/synapse#9624