[WPB-6144] Prevent MLS one-to-one messaging for a blocking user (q1-2024)#3900
Closed
mdimjasevic wants to merge 4 commits intoq1-2024from
Closed
[WPB-6144] Prevent MLS one-to-one messaging for a blocking user (q1-2024)#3900mdimjasevic wants to merge 4 commits intoq1-2024from
q1-2024)#3900mdimjasevic wants to merge 4 commits intoq1-2024from
Conversation
This commit introduces the concept of Subsystems. Each of these subsystems will represent an important part of the domain concepts in the product that will interact with other subsystems. We will use effect systems to encode these subsystems and test them in isolation as much as possible. This commit consolidates all the code that spoke to gundeck from brig and galley into the NotificationSubsystem. https://wearezeta.atlassian.net/browse/WPB-5985 --------- Co-authored-by: Magnus Viernickel <magnus.viernickel@wire.com> Co-authored-by: Leif Battermann <leif.battermann@wire.com>
* Test: no MLS 1-to-1 when a connection is blocked * Test: a test with expected behavior after blocking the connection * Check if sending a msg to 1-to-1 and not connected * Add a changelog * WIP: Debugging a test failure * Update the confirming test * Revert "Check if sending a msg to 1-to-1 and not connected" This reverts commit c4af1508ecf4eac88db83b71d1af35024a7a7de1. * WIP: generalise the Update.blockConv handler * Connections: Also block MLS one2one conv when blocking conn * Test: Parameterise over One2OneScenario * Add the missing connection ID in an internal endpoint * Wrap a function comment for readability * Introduce a Galley internal endpoint: blocking a qualified conversation * WIP: Check if an MLS 1-1 conv exists before blocking What is left to do is to make this check work for an MLS 1-1 conv that can be remote * Make upsertOne2OneConv always take a Conv ID Brig can determine this ID based on protocol of the conversation or read it from the DB. Inventing this in galley causes more trouble for having two One2One convs for proteus and mls. * WIP: Remove user from 1:1 MLS conv when they block someone * WIP: Remove mls clients on connection block * fixup! WIP: Remove mls clients on connection block * Make sure 1-1 conv is established before updating * Finalise the bug-confirming test * Remove debugging output from application code * Fix a changelog * Remove redundant constraints * Properly check if an MLS 1-1 conversation exists before blocking it * Remove more of unused code * Remove an unused connection ID in an internal Galley endpoint for blocking a conv --------- Co-authored-by: Akshay Mankar <akshay@wire.com>
q1-2024)
…ck-from-develop-to-q1-2024
stefanwire
requested changes
Feb 29, 2024
Contributor
stefanwire
left a comment
There was a problem hiding this comment.
Is this PR supposed to merge the new notification subsystem?
2 tasks
Contributor
Author
|
Closing in favor of #3906 . |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a backport of PR #3889 from
developtoq1-2024. The diff is much bigger than PR #3889 because dependent PR #3786 had to be cherry-picked too.Tracked by https://wearezeta.atlassian.net/browse/WPB-6144.
Checklist
changelog.d