-
Notifications
You must be signed in to change notification settings - Fork 333
Merge develop into mls-olaf #3317
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
Conversation
… errors (#3229) * FS-1467: Updates to allow partial success and tests * FS-1467 Setting which conversation actions should be fault tolerant * FS-1467: Fixing tests for unavailable federator * FS-1467: Formatting and linting * FS-1467: Adding changelog * FS-1467: Swapping out a bool for a more descriptive type * FS-1467: Updates from PR comments --------- Co-authored-by: Marko Dimjašević <[email protected]> Co-authored-by: Igor Ranieri <[email protected]>
* Deprecate start-services-only.sh * Fix outdated docs on how to run swagger docs locally.
* Initial import of MLS test framework * Add subconversation utilities to integration suite * Add more utilities * Add self conversation utilities --------- Co-authored-by: Stefan Berthold <[email protected]>
* Add convenience getJSON and getBody functions These can be used to extract the body from a response and check the status code at the same time. * baseRequest now adds Z headers automatically * Added liftIO versions of putStrLn etc * Add Show instances for MLSState --------- Co-authored-by: Stefan Matting <[email protected]>
* Refactoring: make UnreachableUsers a NonEmpty As agreed with client devs on Apr 4, 2023 in the Squad - Federation chat, the absence of the `failed_to_send` field in response to an MLS message send request has the same meaning as an empty list provided in the same field. * executeProposalAction: return failed-to-add users * Move and generalise mockUnreachableFor * Introduce failed to remove (via failed to fetch client info) * Propagate FailedToProcess across federation API arising from conversation updates * Use a V4 add members endpoint in tests * Rethrow the invalid-domain exception * Rethrow federation-not-available error * Fix a golden test for LeaveConversationResponse * Golden tests for MLSMessageSendingStatus * Clean up conv action federation failure handling * Move unreachability stuff into its own module Delete the FederationFailEarly type * Replace tuple with multiple arguments
* Use feature singletons in TeamFeatureStore This introduces a `FeatureSingleton` GADT, which is then used by the Cassandra interpretation of `TeamFeatureStore` to determine how to read and write into the database. Feature singletons avoids having to pass a database-specific constraint to the effect itself, and as a consequence makes it possible to remove the `db` type variable from all the code that uses the `TeamFeature` effect. * Update new feature checklist
This is mostly inspired by our restund Helm chart. max-allocate-lifetime has been removed as it represented the default value. The current config settings were reviewed with Scott. N.B. the CA-file setting is mandatory to use federated certificate whitelisting. Co-authored-by: jschaul <[email protected]>
Introduces a new service: background-worker. The worker watches backend-notification queues corresponding to all the remote domains and pushes the notifications one-by-one. https://wearezeta.atlassian.net/browse/FS-1940 Co-authored-by: Akshay Mankar <[email protected]>
It is only required when federation is enabled.
|
There were a couple of merge conflicts.
/i/user/meta-info
(stern) (Fix:/i/user/meta-info
(stern) #3281)Domain
type everywhere. (UseDomain
type everywhere. #3307)