-
Notifications
You must be signed in to change notification settings - Fork 6
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
fix: delay outgoing message before sync is finished [#WPB-15141] 🍒 #3220
fix: delay outgoing message before sync is finished [#WPB-15141] 🍒 #3220
Conversation
Quality Gate passedIssues Measures |
Bencher Report
Click to view all benchmark results
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #3220 +/- ##
===========================================
- Coverage 54.48% 54.47% -0.01%
===========================================
Files 1269 1269
Lines 36958 36962 +4
Branches 3745 3745
===========================================
- Hits 20135 20134 -1
- Misses 15410 15415 +5
Partials 1413 1413
... and 3 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Datadog ReportBranch report: ✅ 0 Failed, 3293 Passed, 108 Skipped, 1m 3.17s Total Time |
This PR was automatically cherry-picked based on the following PR:
Original PR description:
https://wearezeta.atlassian.net/browse/WPB-15141
What's new in this PR?
Issues
Preconditions:
User opens the app, sync is started and user see some messages that cannot be decrypted in the conversation.
Causes
Solutions
Delay sending delete message until sync is complete. This ensures that message is sent with correct epoch value.
The issue has a broader context. Any message a client sends before sync is complete can cause re-join and break decryption. This should be covered as a part of: https://wearezeta.atlassian.net/browse/WPB-15262