Skip to content
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

dataMoverTopic not required anymore and defaults to empty string #2554

Merged

Conversation

KillianG
Copy link
Contributor

Do not create a consumer if no topic provided

Issue: BB-565

@bert-e
Copy link
Contributor

bert-e commented Oct 10, 2024

Hello killiang,

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 Oct 10, 2024

Incorrect fix version

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

  • None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

  • 8.7.0

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

Copy link

codecov bot commented Oct 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.28%. Comparing base (1540d41) to head (1e7517f).
Report is 7 commits behind head on development/8.7.

Additional details and impacted files

Impacted file tree graph

Files with missing lines Coverage Δ
...tensions/replication/ReplicationConfigValidator.js 60.00% <ø> (ø)
...sions/replication/queueProcessor/QueueProcessor.js 72.96% <100.00%> (ø)
Components Coverage Δ
Bucket Notification 66.66% <ø> (ø)
Core Library 75.12% <ø> (ø)
Ingestion 69.24% <ø> (ø)
Lifecycle 76.20% <ø> (ø)
Oplog Populator 82.95% <ø> (ø)
Replication 57.57% <100.00%> (ø)
Bucket Scanner 85.60% <ø> (ø)
@@               Coverage Diff                @@
##           development/8.7    #2554   +/-   ##
================================================
  Coverage            70.28%   70.28%           
================================================
  Files                  194      194           
  Lines                12965    12965           
================================================
  Hits                  9113     9113           
  Misses                3842     3842           
  Partials                10       10           
Flag Coverage Δ
api:retry 9.75% <0.00%> (ø)
api:routes 9.56% <0.00%> (ø)
bucket-scanner 85.60% <ø> (ø)
ingestion 12.48% <0.00%> (ø)
lib 7.52% <0.00%> (ø)
lifecycle 19.28% <0.00%> (ø)
notification 0.88% <0.00%> (ø)
replication 18.90% <100.00%> (ø)
unit 46.68% <0.00%> (ø)

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

@bert-e
Copy link
Contributor

bert-e commented Oct 10, 2024

Waiting for approval

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

  • the author

  • 2 peers

@KillianG KillianG force-pushed the improvement/BB-565-create-consumer-conditionally branch from 48dc8e7 to 48bbfca Compare October 10, 2024 14:33
@KillianG KillianG force-pushed the improvement/BB-565-create-consumer-conditionally branch from 48bbfca to 62ece50 Compare October 15, 2024 12:04
@KillianG KillianG changed the base branch from development/8.7 to improvement/BB-514-handle-lifecycle-rules October 15, 2024 12:05
@scality scality deleted a comment from bert-e Oct 15, 2024
@KillianG KillianG force-pushed the improvement/BB-565-create-consumer-conditionally branch from 62ece50 to a3d8bf8 Compare October 15, 2024 12:06
@benzekrimaha benzekrimaha force-pushed the improvement/BB-514-handle-lifecycle-rules branch 4 times, most recently from 330558b to 782c8d5 Compare October 23, 2024 13:14
@benzekrimaha benzekrimaha force-pushed the improvement/BB-514-handle-lifecycle-rules branch 5 times, most recently from 957199c to 1540d41 Compare October 29, 2024 10:55
Base automatically changed from improvement/BB-514-handle-lifecycle-rules to development/8.7 October 29, 2024 11:19
@bert-e
Copy link
Contributor

bert-e commented Oct 29, 2024

Conflict

There is a conflict between your branch improvement/BB-565-create-consumer-conditionally and the
destination branch development/8.7.

Please resolve the conflict on the feature branch (improvement/BB-565-create-consumer-conditionally).

git fetch && \
git checkout origin/improvement/BB-565-create-consumer-conditionally && \
git merge origin/development/8.7

Resolve merge conflicts and commit

git push origin HEAD:improvement/BB-565-create-consumer-conditionally

@bert-e
Copy link
Contributor

bert-e commented Oct 29, 2024

Waiting for approval

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

  • the author

  • 2 peers

@KillianG
Copy link
Contributor Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Oct 29, 2024

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

  • ✔️ development/8.7

The following branches have NOT changed:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.5
  • development/8.6

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

Goodbye killiang.

The following options are set: approve

@bert-e bert-e merged commit 1e7517f into development/8.7 Oct 29, 2024
9 checks passed
@bert-e bert-e deleted the improvement/BB-565-create-consumer-conditionally branch October 29, 2024 15:29
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.

6 participants