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.

Sign up for GitHub

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

Jump to bottom

QQ: unblock publishers when queue length policy is deleted (backport #12310) #12314

Merged
merged 2 commits into from
Sep 16, 2024
Merged

QQ: unblock publishers when queue length policy is deleted (backport #12310) #12314

merged 2 commits into from
Sep 16, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Sep 16, 2024

Fixes #12206

Types of Changes

  • Bug fix (non-breaking change which fixes issue #NNNN)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause an observable behavior change in existing systems)
  • Documentation improvements (corrections, new content, etc)
  • Cosmetic change (whitespace, formatting, etc)
  • Build system and/or CI
This is an automatic backport of pull request #12310 done by [Mergify](https://mergify.com).

mkuratczyk and others added 2 commits September 16, 2024 15:54
@mkuratczyk @mergify
Failing test for max-length policy deletion
c447701 
Clearing a max-length policy doesn't unblock existing
publishers. When a new publisher connects, it can publish
to the queue.

(cherry picked from commit ea976e5)
@dcorbacho @mergify
Quorum queues: unblock publishers when clearing max-length policy
b3918cd 
(cherry picked from commit 05f0e03)
@michaelklishin michaelklishin merged commit 7821a27 into v4.0.x Sep 16, 2024
240 checks passed
@michaelklishin michaelklishin deleted the mergify/bp/v4.0.x/pr-12310 branch September 16, 2024 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@dcorbacho dcorbacho

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@michaelklishin @dcorbacho @the-mikedavis @mkuratczyk