Skip to content

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

Merged
merged 4 commits into from
Jul 17, 2025

Conversation

Kerkesni
Copy link
Contributor

@Kerkesni Kerkesni commented Jul 7, 2025

Backport #2655

Issue: BB-697

@bert-e
Copy link
Contributor

bert-e commented Jul 7, 2025

Hello kerkesni,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval
/bypass_build_status Bypass the build and test status
/bypass_commit_size Bypass the check on the size of the changeset TBA
/bypass_incompatible_branch Bypass the check on the source branch prefix
/bypass_jira_check Bypass the Jira issue check
/bypass_peer_approval Bypass the pull request peers' approval
/bypass_leader_approval Bypass the pull request leaders' approval
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request TBA
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Jul 7, 2025

Incorrect fix version

The Fix Version/s in issue BB-697 contains:

  • 9.0.13

  • 9.1.0

Considering where you are trying to merge, I expected to find at least:

  • 9.0.4.2

Please check the Fix Version/s of BB-697, or the target
branch of this pull request.

Copy link

codecov bot commented Jul 7, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.00%. Comparing base (135f9eb) to head (21cb21f).
Report is 4 commits behind head on hotfix/9.0.4.

Additional details and impacted files

Impacted file tree graph

Files with missing lines Coverage Δ
...ensions/notification/NotificationQueuePopulator.js 98.13% <100.00%> (+0.05%) ⬆️
...s/notification/configManager/MongoConfigManager.js 97.87% <100.00%> (+0.07%) ⬆️

... and 5 files with indirect coverage changes

Components Coverage Δ
Bucket Notification 75.57% <100.00%> (+0.19%) ⬆️
Core Library 79.41% <ø> (-0.78%) ⬇️
Ingestion 70.14% <ø> (-0.09%) ⬇️
Lifecycle 76.88% <ø> (-0.21%) ⬇️
Oplog Populator 85.06% <ø> (ø)
Replication 58.56% <ø> (-0.04%) ⬇️
Bucket Scanner 85.60% <ø> (ø)
@@               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              
Flag Coverage Δ
api:retry 9.47% <0.00%> (-0.01%) ⬇️
api:routes 9.29% <0.00%> (-0.01%) ⬇️
bucket-scanner 85.60% <ø> (ø)
ft_test:queuepopulator 8.90% <0.00%> (-1.28%) ⬇️
ingestion 12.55% <0.00%> (-0.02%) ⬇️
lib 7.33% <0.00%> (-0.01%) ⬇️
lifecycle 18.74% <0.00%> (-0.01%) ⬇️
notification 1.07% <9.52%> (+<0.01%) ⬆️
replication 18.52% <0.00%> (-0.01%) ⬇️
unit 48.58% <100.00%> (+0.02%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@williamlardier williamlardier left a 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 🙂

@Kerkesni Kerkesni force-pushed the bugfix/BB-697-backport-9.0.4 branch 2 times, most recently from 5d0588a to 313bb9b Compare July 8, 2025 10:17
@Kerkesni
Copy link
Contributor Author

Kerkesni commented Jul 8, 2025

Closing PR as no release of ARTESCA 3.1.3 is currently planned.

@Kerkesni Kerkesni closed this Jul 8, 2025
@Kerkesni Kerkesni reopened this Jul 17, 2025
Kerkesni added 2 commits July 17, 2025 13:25
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
@Kerkesni Kerkesni force-pushed the bugfix/BB-697-backport-9.0.4 branch from 313bb9b to 096dbd3 Compare July 17, 2025 11:26
@bert-e
Copy link
Contributor

bert-e commented Jul 17, 2025

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

@Kerkesni
Copy link
Contributor Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Jul 17, 2025

Build failed

The build for commit did not succeed in branch bugfix/BB-697-backport-9.0.4

The following options are set: approve

@Kerkesni Kerkesni force-pushed the bugfix/BB-697-backport-9.0.4 branch 2 times, most recently from 6440bf9 to 6d18072 Compare July 17, 2025 12:12
Kerkesni added 2 commits July 17, 2025 14:21
Debian Buster repositories are no longer available.
Debian Buster reached end-of-life and has been moved to archive repositories

Issue: BB-697
@Kerkesni Kerkesni force-pushed the bugfix/BB-697-backport-9.0.4 branch from 6d18072 to 21cb21f Compare July 17, 2025 12:22
@bert-e
Copy link
Contributor

bert-e commented Jul 17, 2025

Build failed

The build for commit did not succeed in branch bugfix/BB-697-backport-9.0.4

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Jul 17, 2025

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ hotfix/9.0.4

The following branches have NOT changed:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.6
  • development/9.0
  • development/9.1

Please check the status of the associated issue BB-697.

Goodbye kerkesni.

The following options are set: approve

@bert-e bert-e merged commit 21cb21f into hotfix/9.0.4 Jul 17, 2025
25 of 30 checks passed
@bert-e bert-e deleted the bugfix/BB-697-backport-9.0.4 branch July 17, 2025 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants