-
Notifications
You must be signed in to change notification settings - Fork 325
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
integration: Fix testAddingUserNonFullyConnectedFederation and testNotificationsForOfflineBackends #3529
Conversation
-- FUTUREWORK: deleteAllFedConns at the time of acquiring a backend, so | ||
-- tests don't affect each other. | ||
deleteAllFedConns dynBackend | ||
void $ createFedConn dynBackend (FedConn own "full_search") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please explain how this dance of deleting and then immediately making a connection works?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you have two tests: one of them connects dynBackend1
with all backends and second one only connects dynBackend
1 with OwnDomain
. if the first test runs first, the second test will always fail. So, the second test must always delete all the connections dynBackend1
has and then only create a connection with OwnDomain
to ensure that it is not affected by the first test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see.
Wasn't the plan to provide more isolation between test executions? This dance within the test is very fragile, it incurs what I hope can be called a needless brain load, and is not a general solution.
Is there something we can do in the (dynamic) backend setup that would make them isolated from each other (even if we go with e.g. randomly assigning identifiers (names) and such, which should be good enough if they are very unlikely to collide)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that's why I added the FUTUREWORK. While acquiring an environment we could simply truncate the table which keeps this information around.
df65819
to
7750466
Compare
…ipating backends is down
7750466
to
25437f4
Compare
-- void $ awaitNotification downUser1 downClient1 (Just newMsgNotif) 1 isOtherUser2LeaveUpConvNotif | ||
-- void $ awaitNotification otherUser otherClient (Just newMsgNotif) 1 isDelUserLeaveDownConvNotif |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you planning to uncomment or remove these two lines?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, see the comment above them. These don't work due to a bug: https://wearezeta.atlassian.net/browse/WPB-3664
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, but please do something with the two commented out lines at the bottom of changes in the test module Federation.hs
.
* Fix bug: federatorInternal host not set for background-worker (#3516) * WPB-3916: Filtering out duplicate members when sending defederation notifications (#3515) * integration: Add test to verify behaviour with offline backends (#3501) * background-worker: Make push backoff times configurable * brig/getFederationStatus: Always return NonConnectedBackends as empty when fed policy is AllowAll * integration: Use separate vHosts for backendA and B. * integration/RunServices: Add hack to make federation work * integration: Add test to verify behaviour with offline backends * helm-var-integration: Workaround bug with federation * integration-test.sh: Run new integration test suite first --------- Co-authored-by: Marko Dimjašević <marko.dimjasevic@wire.com> * Distinguish between update and upsert cassandra commands (#3513) * Remove billing-team-member-backfill tool (#3520) * dockerephemeral: Increase nofile ulimits for ES and Fake DynamoDB (#3521) * [WPB 3842] Federation completeness check (#3514) * WPB-3842: Improving checks for adding users to a conversation. Added a check to `ensureAllowed` that checks for full federation connections for domains in a conversation, including the domains for new users. * WPB-3842: Adding the changelog * WPB-3842: Moving where the extra domain checks are being performed. Updating integration tests to reflect the updated semantics of conversation join semantics. Many of them weren't expecting errors relating to unreachable domains, and had to be updated to reflect this. * Fix asserted domains in an integration test * Integration test: assert on non-federating domains * WPB-3842: Changing parallel testing to sequential testing --------- Co-authored-by: Marko Dimjašević <marko.dimjasevic@wire.com> * WPB-3798 incorrect json field names (#3518) * WPB-3798: Updating code and tests after renaming fields * WPB-3798: More updates to names after finding more JSON prefix mangling * WPB-3798: Fixing schema instances for SAML data * WPB-3798: Fixing instances that had errors, found by tests * WPB-3798: Adding changelogs * WPB-3798: PR feedback. * WPB-3798: Fixing an error with a field called `data'` The trailing ' would end up in the JSON representation. I've changed it to use a leading `_` like other structures, and wrote a newtype to handle the minimal prefix stripping. Also cleaning up the diff in regards to imports. * WPB-3798: Cleaning up imports to minimise the diff * nit-picks (#3519) * Remove unneeded -Wwarn (re-enabeling -Werror in those modules). * Makefile: fix hspec_options overloading in .envrc.local. * integration: Fix testAddingUserNonFullyConnectedFederation and testNotificationsForOfflineBackends (#3529) * integration: Fix testAddingUserNonFullyConnectedFederation * integration: Don't allow adding users to conv when one of the pariticipating backends is down * integration: Add retries to get around problem of federation domain sync threads * Introduce API v5 (#3527) * Introduce development version 5 * Specialise API to a specific version * Use versioned swagger for galley * Use version swagger for all other services * Collect all service Swaggers into a typeclass * Fix swagger integration tests * Revert any changes to API versions before 5 * Remove promotion of isDevelopmentVersion * Add CHANGELOG entry * stern: Optimize RAM usage of /i/users/meta-info (#3522) * stern: Fetch only the notifications that are needed * stern: Fetch only the conversations that are needed * Integration tests: use static ports (#3536) * [WPB-3799] cannot fetch conversation details after connection request (#3538) * brig-integration: Fix flaky tests for API.Federation (#3539) * brig-integration: Don't assume only 1 result in search by display name Display names are random strings from 2 to 128 characters. If a 2 string name gets generated it is likely that it matches some name generated in another test. * brig-integration: Mark test not flaky It didn't fail after runnning it 1000 times. * Integration suite: Fix bug in local setup: wrong port for nginz http2 (#3543) * [WPB-662] servantify brig provider bot api (#3540) * Fix broken "we are hiring" link (#3549) * Multi-ingress guest links (#3546) * Check validity of notification IDs (#3550) * Check validity of notification IDs * Add CHANGELOG entry * fixup! Add CHANGELOG entry * fixup! fixup! Add CHANGELOG entry * WPB-633 Servantify Brig/Provider.Service API (#3554) * WPB-1214: Servantify Brig/Provider.Service API - Moving the routes over to servant, and removing the old routing code. - Adding new instances to types that needed them for servant. * WPB-663: Removing a redundant TODO comment, adding changelog * Fix ES migration script. (#3558) * Revert "WPB-633 Servantify Brig/Provider.Service API (#3554)" This reverts commit 3653d56. * Integration tests: delete all rabbitmq queues during dynamic backends setup phase (#3523) * [WPB-4406] federator improve logging (#3556) * Makefile: Avoid executing the hint (#3564) Backticks execute the command even when they are in quotes. * Finalise v4 (#3545) * Remove MLS endpoints from the API They will be reintroduced when merging the mls branch. These endpoints are not currently functional on develop, so removing them from here will reduce the amount of conflicts. * Finalise v4 * Add CHANGELOG entry * Add pregenerated swagger for v4 * Delete MLS tests in brig * Remove more MLS endpoints from v4 * Set default API version to 5 in integration tests * Update the documentation on API versioning --------- Co-authored-by: Marko Dimjašević <marko.dimjasevic@wire.com> * Fix: SCIM user lookup after changing IdP issuer ID (#3473) * doc: document webapp configuration for multi-ingress environments (#3569) --------- Co-authored-by: Sven Tennie <sven.tennie@gmail.com> * [WPB-4361] upgrade jwt-tools (#3559) * cassandra: Add column and table names in parsing error messages (#3555) * s/CORS/CSP/ as mentionned by Sven in WPB-2912 * Replace broken integrations with links see WPB-3599 * replace all instances of example.com with wire.example as per wpb-2621, in charts only * change back from wire.example to example.com as this was mistakenly commit to develop instead of to the proper branch * add documentation on creating a first user * reverting previous commit as sent to wrong branch * Update sftd docs: include uri scheme in allowOrigin (#3584) * Update sftd docs: include uri scheme in allowOrigin * fixup * WPB-4629 impossible to add users to a conversation if one of the members is from an offline backend (#3585) * fake-aws-s3 chart: Upgrade to minio 5.0.13 (#3565) * Disable de-federation to avoid running into a scalability issue (#3582) https://wearezeta.atlassian.net/browse/WPB-4668 Co-authored-by: Akshay Mankar <akshay@wire.com> * [WPB-3664] Bug fix: Notify remote backends of their users removed from conversation when reachable again (#3537) * Formatting * Test utilities for changing a conv name * Add a test confirming the bug report * An action to enqueue notifications concurrently * Enqueue member removal notification for remotes * Add a changelog * Test case formatting * Migrate test roleUpdateWithRemotesUnavailable * Migrate test putReceiptModeWithRemotesOk * Migrate test putReceiptModeWithRemotesUnavailable * Migrate test testRoleUpdateWithRemotesOk * Migrate test roleUpdateRemoteMember * Migrate test putQualifiedConvRenameWithRemotesUnavailable This one is already covered by testSynchroniseUserRemovalNotification * Migrate test putQualifiedConvRenameWithRemotesOk * Migrate test deleteLocalMemberConvLocalQualifiedOk * Migrate test deleteRemoteMemberConvLocalQualifiedOk * Migrate test deleteUnavailableRemoteMemberConvLocalQualifiedOk * Add the copyright header to a test module * Move a test utility (allPreds) * Test utility: create a team with members * Migrate test testAccessUpdateGuestRemoved * Migrate test messageTimerChangeWithRemotes * Migrate test messageTimerUnavailableRemotes * Migrate test testAccessUpdateGuestRemovedRemotesUnavailable * Migrate test accessUpdateWithRemotes * Migrate test testAddRemoteMember * Migrate test testDeleteTeamConversationWithRemoteMembers * Migrate test testDeleteTeamConversationWithUnavailableRemoteMembers * Move a test utility (assertLeaveNotification) * Migrate test "POST /federation/leave-conversation : Success" * Migrate test "POST /federation/on-user-deleted-conversations : Remove deleted remote user from local conversations" * Migrate test updateConversationByRemoteAdmin * Tests: support giving a role when adding * Use cannon API for notifications when possible * Use startDynamicBackends when possible * Fix assertion * Migrate test testAddRemoteUsersToLocalConv * Test add member endpoint at version 1 * Add return value to enqueueNotification * Use cannon assertions in offline backends test * Check that remote notifications are received * Test removal of users from unreachable backends * Use correct domains for default backends Taking the domains in the `backendA` and `backendB` resources only works locally. * fixup! Use cannon assertions in offline backends test --------- Co-authored-by: Paolo Capriotti <paolo@capriotti.io> Co-authored-by: Akshay Mankar <akshay@wire.com> * WPB-4240: Migrate from swagger2 to openapi3 (#3570) --------- Co-authored-by: Igor Ranieri Elland <54423+elland@users.noreply.github.com> Co-authored-by: Igor Ranieri <igor@elland.me> * Remove mocked MLS member add test * Resolve conflict in pregenerated swagger * Remove MLS end2end tests --------- Co-authored-by: Stefan Matting <smatting@users.noreply.github.com> Co-authored-by: Owen Harvey <owenlharvey@gmail.com> Co-authored-by: Akshay Mankar <akshay@wire.com> Co-authored-by: Marko Dimjašević <marko.dimjasevic@wire.com> Co-authored-by: fisx <mf@zerobuzz.net> Co-authored-by: Igor Ranieri Elland <54423+elland@users.noreply.github.com> Co-authored-by: Leif Battermann <leif.battermann@wire.com> Co-authored-by: Jappie Klooster <jappieklooster@hotmail.com> Co-authored-by: Leif Battermann <leifbattermann@gmail.com> Co-authored-by: Thomas Belin <thomasbelin4@gmail.com> Co-authored-by: Sven Tennie <sven.tennie@gmail.com> Co-authored-by: Arthur Wolf <wolf.arthur@gmail.com> Co-authored-by: Igor Ranieri <igor@elland.me>
…tificationsForOfflineBackends (#3529) * integration: Fix testAddingUserNonFullyConnectedFederation * integration: Don't allow adding users to conv when one of the pariticipating backends is down * integration: Add retries to get around problem of federation domain sync threads
https://wearezeta.atlassian.net/browse/WPB-3974
Checklist
Add a new entry in an appropriate subdirectory ofNo changelog, insignificant change.changelog.d