Skip to content

fix: make sure RabbitMQ broker’s enqueue() attempts the correct number of preset retries#669

Merged
Bogdanp merged 1 commit into
Bogdanp:masterfrom
jenstroeger:master
Dec 22, 2024
Merged

fix: make sure RabbitMQ broker’s enqueue() attempts the correct number of preset retries#669
Bogdanp merged 1 commit into
Bogdanp:masterfrom
jenstroeger:master

Conversation

@jenstroeger

Copy link
Copy Markdown
Contributor

Closes #668

Comment thread dramatiq/brokers/rabbitmq.py
@jenstroeger jenstroeger marked this pull request as ready for review December 22, 2024 08:25
@Bogdanp Bogdanp merged commit b372f43 into Bogdanp:master Dec 22, 2024
@Bogdanp

Bogdanp commented Dec 22, 2024

Copy link
Copy Markdown
Owner

Thanks again!

@jenstroeger

Copy link
Copy Markdown
Contributor Author

@Bogdanp I stumbled upon this minor bug when I was investigating this: Issue with RabbitMQ Broker: sending a message to the queue creates a consumer thread locally.

Could you please take a look? I can open a PR with the proposed solution which works locally, but somehow I’m not too sure if that’s a good solution, it feels a little awkward.

LincolnPuzey added a commit to LincolnPuzey/dramatiq that referenced this pull request Jul 14, 2025
`attempts` variable is counting the number of attempts made.
Once this is >= to the max, raise Exception.
Also update log message to make this more obvious
aequitas pushed a commit to aequitas/dramatiq that referenced this pull request Nov 17, 2025
`attempts` variable is counting the number of attempts made.
Once this is >= to the max, raise Exception.
Also update log message to make this more obvious
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.

RabbitMQ Broker off-by-one error when reattempting ensuring a queue

2 participants