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

[documentation] broker_connection_max_retries of 0 does not mean "retry forever" #8626

Merged
merged 1 commit into from Nov 10, 2023

Conversation

jakila
Copy link
Contributor

@jakila jakila commented Nov 9, 2023

This PR updates the documentation regarding broker_connection_max_retries. As I learned the hard way, a value of 0 does not mean "retry forever".

Reasoning:

update documentation of broker_connection_max_retries as a value of 0 does not mean "retry forever"
Copy link
Member

@auvipy auvipy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems like a great catch

@auvipy auvipy added this to the 5.3.x milestone Nov 10, 2023
@auvipy auvipy merged commit 7d7b9a7 into celery:main Nov 10, 2023
6 checks passed
@jakila jakila deleted the patch-1 branch November 14, 2023 12:58
Uxio0 added a commit to safe-global/safe-transaction-service that referenced this pull request Apr 12, 2024
- `0` does not mean retry forever
- celery/celery#8626
Uxio0 added a commit to safe-global/safe-transaction-service that referenced this pull request Apr 15, 2024
- `0` does not mean retry forever
- celery/celery#8626
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

None yet

2 participants