"Retry and timeout are misconfigured" as per default settings
See original GitHub issueOn a fresh installation without altered configuration, the new warning pops up:
/usr/lib/python3.9/site-packages/django_q/conf.py:136: UserWarning: Retry and timeout are misconfigured. Set retry larger than timeout,
failure to do so will cause the tasks to be retriggered before completion.
See https://django-q.readthedocs.io/en/latest/configure.html#retry for details.
warn("""Retry and timeout are misconfigured. Set retry larger than timeout,
Since I did not change any configuration, I looked up the default conf.py in this repo to find that timeout is set to none while retry is set to 60s. Should the the timeout in the default conf.py be set to an appropriate value so that it does not trigger the new warning after an unaltered default installation?
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Configuration — Django Q 1.3.6 documentation - Read the Docs
Defaults to 60. The value must be bigger than the time it takes to complete longest task, i.e. timeout must be less than...
Read more >"Retry and timeout are misconfigured" as per default settings
"Retry and timeout are misconfigured" as per default settings.
Read more >Automatic Retries. How to configure Envoy's retry… |
Envoy provides a simple configuration option for retrying requests. Consider specifics of your system as you set up retries across each route:.
Read more >MigrationWiz - Failures & Error States - BitTitan Help Center
MigrationWiz contains a mode in which you can resubmit the migration to retry failed items. This mode of operation is always free of...
Read more >Advanced content caching settings on Mac - Apple Support
Key Description Default value
AllowImports Allows import (upload) requests. Yes
MetricsInterval 60 (seconds)
Parents none
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, and the docs need to be updated too. It happened because of a recent PR. Either that or we don’t show the warning on no timeout configured.
Is this warning safe to ignore if there is no timeout configured?