-
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 client init [WPB-15022] 🍒 #3181
Conversation
* fix: secure mls client creation with is mls enabled * fix: dont persist mls conversations when mls is disabled * review improvements
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 #3181 +/- ##
========================================
Coverage 54.14% 54.14%
========================================
Files 1252 1252
Lines 36528 36547 +19
Branches 3703 3710 +7
========================================
+ Hits 19777 19788 +11
- Misses 15326 15330 +4
- Partials 1425 1429 +4
... and 3 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Datadog ReportBranch report: ✅ 0 Failed, 3242 Passed, 107 Skipped, 1m 0.99s Total Time |
This PR was automatically cherry-picked based on the following PR:
Original PR description:
PR Submission Checklist for internal contributors
The PR Title
SQPIT-764
The PR Description
What's new in this PR?
Issues
There is scenario when mls client can be created when mls feature config is disabled
Causes (Optional)
Before enabling MLS on feature config backend can change
cipherSuiteTag
causing encryption problems when user can already use some defaultcipherSuiteTag
if he created MLS client earlier.Solutions
MLSFailure.Disabled
MLSKeyPackageCountUseCase
to not fetch key package count when MLS is disabled by feature config