-
Notifications
You must be signed in to change notification settings - Fork 13k
feat: Make Omnichannel room opening transactional #34958
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
|
Looks like this PR is not ready to merge, because of the following issues:
Please fix the issues and try again If you have any trouble, please check the PR guidelines |
🦋 Changeset detectedLatest commit: 6912ac2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 35 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 #34958 +/- ##
===========================================
- Coverage 59.17% 59.17% -0.01%
===========================================
Files 2822 2820 -2
Lines 68118 67693 -425
Branches 15145 15071 -74
===========================================
- Hits 40312 40060 -252
+ Misses 24975 24814 -161
+ Partials 2831 2819 -12
Flags with carried forward coverage won't be shown. Click here to find out more. |
Proposed changes (including videos or screenshots)
This aims to prevent orphan rooms caused by some actions timing out, or just the process timing out.
An orphan room could be a room with no inquiry, or, the incredible case (?), an inquiry without a room. This happens because there were some actions in between the room creation and the inquiry creation that could fail, leaving a room with no inquiry. There was the posibiity of the inquiry creation failing, which would leave the room orphaned as well.
Since now both are in a transaction, they should be always created altogether, making it safer and less error prone.
Issue(s)
https://rocketchat.atlassian.net/browse/CORE-929
Steps to test or reproduce
Further comments