-
Notifications
You must be signed in to change notification settings - Fork 13k
fix: Allow queue to recover from some errors #36256
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: 1f3fa47 The changes in this PR will be included in the next version bump. This PR includes changesets to release 37 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 ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #36256 +/- ##
========================================
Coverage 64.81% 64.82%
========================================
Files 3153 3153
Lines 104788 104789 +1
Branches 19963 19956 -7
========================================
+ Hits 67923 67925 +2
+ Misses 34178 34174 -4
- Partials 2687 2690 +3
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
/patch |
|
Pull request #36270 added to Project: "Patch 7.7.2" |
Proposed changes (including videos or screenshots)
Issue(s)
https://rocketchat.atlassian.net/browse/CTZ-229
Steps to test or reproduce
Further comments
There was exactly one function that was not covered in a try/catch, cause the only way for it to fail was for Mongo to actually fail... guess what happened