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
"Retry and timeout are misconfigured" as per default settings #526
Comments
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. |
Awesome! I can create the pull request, but I don't know what timeout value would be sane. 30? 59? |
As suggested in Koed00#526
As suggested in Koed00#526
I just had this issue on a fresh install with version 1.3.9 which is surprising since it looks like this PR was merged back in May... |
It was not merged, only the modification in the documentation. I suggested the corresponding code modification in a separate pull request, but my code edits seem to create trouble elsewhere. Unfortunately, I do not know any python and cannot help any further. |
Ah ok, thanks for confirming! |
Is this warning safe to ignore if there is no timeout configured? |
The same issue comes when we set the timeout value to How can we set timeout value to |
On a fresh installation without altered configuration, the new warning pops up:
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?
The text was updated successfully, but these errors were encountered: