Repository navigation
Change Queue default to durable=True - #164
Merged
Merged
Conversation
RabbitMQ 4.3 rejects transient non-exclusive queues with INTERNAL_ERROR (Feature `transient_nonexcl_queues` is deprecated). With the old default of durable=False, Queue(channel, name).declare() fails on RabbitMQ 4.3. - Set the durable default to True in Queue.__init__ and on the class. - Update the unit tests that assert the default. - Add a breaking-change entry to the version history. This is a breaking change. If a durable queue with the same name already exists, a declare with durable=False now fails, and the reverse is also true. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner
Author
|
PR monitor summary: all CI checks pass (test 3.11, 3.12, 3.13, 3.14 and CodeRabbit). CodeRabbit reviewed HEAD 8ec2bdc and found 0 actionable comments. There are 0 unresolved review threads. No code changes were necessary. The PR is not merged. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
rabbitpy.Queuenow defaults todurable=True, soQueue(channel, name).declare()works on RabbitMQ 4.3.Problem
RabbitMQ 4.3 rejects transient non-exclusive queues and closes the connection with
INTERNAL_ERROR - Feature transient_nonexcl_queues is deprecated. With the old default ofdurable=False, the simplest use ofQueuefails on current brokers. CodeRabbit raised this on #163.Solution
durabledefault toTrueinQueue.__init__and on the class.docs/history.mdunder "Unreleased".rabbitpy.simple.create_queuealready defaults todurable=True, so the two APIs now agree.Breaking change: if a queue with the same name already exists as non-durable, the declare now fails with
AMQPPreconditionFailed. The reverse is also true. To keep the old behaviour, passdurable=False. On RabbitMQ 4.3, also passexclusive=True. Release this as a major version (4.0.0).Tests: 369 pass locally against RabbitMQ 4.3.6.
🤖 Generated with Claude Code
Summary by CodeRabbit
Changes
Documentation