Skip to content
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): set removal-keys for 1on1 calls from conversation-response (WPB-10743) πŸ’ πŸ’ #3041

Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 26, 2024

BugWPB-10743 [Android] Use proper MLS removal key with federated 1:1 conversations

This PR was automatically cherry-picked based on the following PR:

Original PR description:


This PR was automatically cherry-picked based on the following PR:

Original PR description:



PR Submission Checklist for internal contributors

  • The PR Title

    • conforms to the style of semantic commits messagesΒΉ supported in Wire's Github WorkflowΒ²
    • contains a reference JIRA issue number like SQPIT-764
    • answers the question: If merged, this PR will: ... Β³
  • The PR Description

    • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

What's new in this PR?

Fetch and set removal-keys from the create-conversation response for 1on1 conversations and only APIV6

Testing

Test Coverage (Optional)

  • I have added automated test to this contribution

PR Post Submission Checklist for internal contributors (Optional)

  • Wire's Github Workflow has automatically linked the PR to a JIRA issue

PR Post Merge Checklist for internal contributors

  • If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

References
  1. https://sparkbox.com/foundry/semantic_commit_messages
  2. https://github.com/wireapp/.github#usage
  3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

@github-actions github-actions bot added cherry-pick PR is cherry-picking changes from another banch echoes: unplanned Any work item that isn’t part of the product or technical roadmap. echoes: product-roadmap Work aligned with the customer-announced roadmap, targeting a specific release date. type: bug / fix 🐞 πŸ‘• size: M 🚨 Potential breaking changes labels Sep 26, 2024
Copy link

sonarqubecloud bot commented Oct 1, 2024

Copy link
Contributor Author

github-actions bot commented Oct 1, 2024

Test Results

3β€ˆ212 tests  +2   3β€ˆ106 βœ… +2   4m 0s ⏱️ -8s
β€‡β€ˆ551 suites Β±0β€‚β€ƒβ€ƒβ€‡β€ˆ106 πŸ’€ Β±0 
β€‡β€ˆ551 files   Β±0β€‚β€ƒβ€ƒβ€‡β€ˆβ€‡β€‡0 ❌ Β±0 

Results for commit c5b3f2c. ± Comparison against base commit 27fc353.

♻️ This comment has been updated with latest results.

Copy link
Contributor Author

github-actions bot commented Oct 1, 2024

🐰 Bencher Report

Branchfix/federated-1on1-removal-keys-cherry-pick-cherry-pick
Testbedubuntu-latest

⚠️ WARNING: The following Measure does not have a Threshold. Without a Threshold, no Alerts will ever be generated!

Click here to create a new Threshold
For more information, see the Threshold documentation.
To only post results if a Threshold exists, set the --ci-only-thresholds CLI flag.

Click to view all benchmark results
BenchmarkLatencynanoseconds (ns)
com.wire.kalium.benchmarks.logic.CoreLogicBenchmark.createObjectInFilesπŸ“ˆ view plot
⚠️ NO THRESHOLD
700,971.81
com.wire.kalium.benchmarks.logic.CoreLogicBenchmark.createObjectInMemoryπŸ“ˆ view plot
⚠️ NO THRESHOLD
341,961,072.89
com.wire.kalium.benchmarks.persistence.MessagesNoPragmaTuneBenchmark.messageInsertionBenchmarkπŸ“ˆ view plot
⚠️ NO THRESHOLD
946,587,869.87
com.wire.kalium.benchmarks.persistence.MessagesNoPragmaTuneBenchmark.queryMessagesBenchmarkπŸ“ˆ view plot
⚠️ NO THRESHOLD
21,344,391.79
🐰 View full continuous benchmarking report in Bencher

@codecov-commenter
Copy link

Codecov Report

Attention: Patch coverage is 15.29412% with 72 lines in your changes missing coverage. Please review.

Project coverage is 52.51%. Comparing base (27fc353) to head (c5b3f2c).

Files with missing lines Patch % Lines
...lium/logic/data/conversation/ConversationMapper.kt 3.33% 28 Missing and 1 partial ⚠️
...om/wire/kalium/network/api/model/ApiModelMapper.kt 0.00% 18 Missing ⚠️
.../network/api/v6/authenticated/ConversationApiV6.kt 0.00% 11 Missing ⚠️
...authenticated/conversation/ConversationResponse.kt 0.00% 10 Missing ⚠️
...ogic/data/mlspublickeys/MLSPublicKeysRepository.kt 57.14% 2 Missing and 1 partial ⚠️
...gic/data/conversation/MLSConversationRepository.kt 83.33% 0 Missing and 1 partial ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #3041      +/-   ##
===========================================
- Coverage    52.56%   52.51%   -0.06%     
===========================================
  Files         1303     1303              
  Lines        50104    50174      +70     
  Branches      4671     4679       +8     
===========================================
+ Hits         26338    26349      +11     
- Misses       21884    21939      +55     
- Partials      1882     1886       +4     
Files with missing lines Coverage Ξ”
...c/data/conversation/ConversationGroupRepository.kt 91.09% <100.00%> (+0.05%) ⬆️
...gic/data/conversation/MLSConversationRepository.kt 83.72% <83.33%> (-0.18%) ⬇️
...ogic/data/mlspublickeys/MLSPublicKeysRepository.kt 30.00% <57.14%> (+20.00%) ⬆️
...authenticated/conversation/ConversationResponse.kt 0.00% <0.00%> (ΓΈ)
.../network/api/v6/authenticated/ConversationApiV6.kt 0.00% <0.00%> (ΓΈ)
...om/wire/kalium/network/api/model/ApiModelMapper.kt 0.00% <0.00%> (ΓΈ)
...lium/logic/data/conversation/ConversationMapper.kt 58.40% <3.33%> (-4.03%) ⬇️

... and 4 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Ξ” = absolute <relative> (impact), ΓΈ = not affected, ? = missing data
Powered by Codecov. Last update 27fc353...c5b3f2c. Read the comment docs.

@datadog-wireapp
Copy link

Datadog Report

Branch report: fix/federated-1on1-removal-keys-cherry-pick-cherry-pick
Commit report: 105efef
Test service: kalium-jvm

βœ… 0 Failed, 3106 Passed, 106 Skipped, 12.37s Total Time

@MohamadJaara MohamadJaara added this pull request to the merge queue Oct 1, 2024
Merged via the queue into develop with commit c667979 Oct 1, 2024
22 checks passed
@MohamadJaara MohamadJaara deleted the fix/federated-1on1-removal-keys-cherry-pick-cherry-pick branch October 1, 2024 13:37
MohamadJaara added a commit that referenced this pull request Oct 18, 2024
…(WPB-10743) πŸ’ πŸ’ (#3041)

* Commit with unresolved merge conflicts

* fix merge conflicts

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Mohamad Jaara <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick PR is cherry-picking changes from another banch echoes: product-roadmap Work aligned with the customer-announced roadmap, targeting a specific release date. echoes: unplanned Any work item that isn’t part of the product or technical roadmap. 🚨 Potential breaking changes πŸ‘• size: M type: bug / fix 🐞
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants