fix: Don't return users with E2ESuggestedKey set when selecting users to provide E2EKey#33405
Conversation
…ning key exchange
|
Looks like this PR is ready to merge! 🎉 |
🦋 Changeset detectedLatest commit: a698950 The changes in this PR will be included in the next version bump. This PR includes changesets to release 33 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #33405 +/- ##
========================================
Coverage 58.58% 58.59%
========================================
Files 2737 2737
Lines 65679 65708 +29
Branches 14824 14826 +2
========================================
+ Hits 38479 38500 +21
- Misses 24421 24429 +8
Partials 2779 2779
Flags with carried forward coverage won't be shown. Click here to find out more. |
sampaiodiego
left a comment
There was a problem hiding this comment.
we agreed to work on API tests in a further task
sampaiodiego
left a comment
There was a problem hiding this comment.
we agreed to work on API tests in a further task
…rs to provide E2EKey (#33405)
Proposed changes (including videos or screenshots)
This should prevent an issue where a user may receive an indefinite amount of "suggested keys" from all the users on a room even when a user already suggested a key for them, duplicating the work.
Now, the endpoint that returns users waiting for keys will return only users that don't have neither
E2EKeynorE2ESuggestedKey.Issue(s)
https://rocketchat.atlassian.net/browse/E2EE2-72
Steps to test or reproduce
Further comments