-
Notifications
You must be signed in to change notification settings - Fork 20
Fix handling of buckets with disabled bucket notifications #2656
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
Hello kerkesni,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files
... and 5 files with indirect coverage changes
@@ Coverage Diff @@
## hotfix/9.0.4 #2656 +/- ##
================================================
- Coverage 73.36% 73.00% -0.37%
================================================
Files 201 201
Lines 13374 13380 +6
================================================
- Hits 9812 9768 -44
- Misses 3552 3602 +50
Partials 10 10
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
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.
Please backport the latest changes before merging 🙂
5d0588a
to
313bb9b
Compare
|
Added try/catch to _processObjectEntry to catch exception and log them before returning an error Issue: BB-697
When bucket notifications are disabled after being enabled, the configuration is set to an empty object. Previously, this case was not handled properly, leading to crashes as the notification producer and processor incorrectly considered the configuration available. This fix ensures proper handling of empty configurations to prevent such issues. Issue: BB-697
313bb9b
to
096dbd3
Compare
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
|
/approve |
Build failedThe build for commit did not succeed in branch bugfix/BB-697-backport-9.0.4 The following options are set: approve |
6440bf9
to
6d18072
Compare
6d18072
to
21cb21f
Compare
Build failedThe build for commit did not succeed in branch bugfix/BB-697-backport-9.0.4 The following options are set: approve |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue BB-697. Goodbye kerkesni. The following options are set: approve |
Backport #2655
Issue: BB-697