-
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(mls): fetch other user supported protocols when resolving 1:1 conversation [WPB-5048] #2418
Conversation
…rted-protocols-when-resolving-conversation-cherry-pick
Test Results2 061 tests - 813 2 031 ✔️ - 738 15s ⏱️ - 2m 23s Results for commit 5035fec. ± Comparison against base commit 290c358. This pull request removes 2874 and adds 2061 tests. Note that renamed tests count towards both.
This pull request removes 105 skipped tests and adds 30 skipped tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #2418 +/- ##
=============================================
+ Coverage 58.39% 58.41% +0.02%
Complexity 21 21
=============================================
Files 1162 1162
Lines 44790 44812 +22
Branches 4181 4184 +3
=============================================
+ Hits 26153 26175 +22
+ Misses 16754 16752 -2
- Partials 1883 1885 +2
... and 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Datadog ReportAll test runs ✅ 2 Total Test Services: 0 Failed, 2 Passed Test Services
|
Cherry pick from the original PR:
PR Submission Checklist for internal contributors
The PR Title
The PR Description
What's new in this PR?
Issues
We're not fetching the supported protocols by the other user in all scenarios when resolving 1:1
Causes
Not yet implemented.
Solutions
Re-fetch the supported protocols when processing events and performing actions. In places, like:
Added a flag that tells if this behaviour is wanted or not in the .
In case of a failure during fetching, just accept whatever is in the DB to avoid bumps due to connection flakyness.
Testing
Test Coverage
PR Post Merge Checklist for internal contributors
References