MamManager: Fix missing unencrypted messages #662
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
lnjX
force-pushed
the
fix/mam-unencrypted-messages-not-processed
branch
from
03ae40b
to
1c0bfa3
Compare
lnjX
force-pushed
the
fix/mam-unencrypted-messages-not-processed
branch
from
1c0bfa3
to
3f3e35c
Compare
There were also some async issues that are now solved, especially when all decryption jobs finished instantly (or no message were encrypted).
lnjX
force-pushed
the
fix/mam-unencrypted-messages-not-processed
branch
from
3f3e35c
to
36b8506
Compare
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.
No description provided.