Persist unsent messages for subsequent sessions #1655
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@gsouquet What's the status of this one? Looks like perhaps merging develop to get the cross-signing test fix would get things moving again? |
Yeah, I was waiting on ops to give me access to BuildKite so that I can re-run the pipelines, but can do that too 👍 |
t3chguy
reviewed
Apr 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes element-hq/element-web#7177
This pull requests hooks into the
Room#_pendingEventListflow to store a serialised version of an unsentMatrixEvent.The storage key is:
mx_pending_events_${roomId}Upon instanciation the
Roommodel will query the storage and populate_pendingEventListif required. Element then picks up the unsent messages and display theRoomStatusBarand a user can decide whether to send or cancel the queued messages