Timeout from commandline not being passed through correctly? #2564
Unanswered
pjmattal-jaide
asked this question in
Potential Issue
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
After upgrading uvicorn from 0.32.1 to 0.34.0, the 300s timeout we were passing via -t on the gunicorn commandline stopped working correctly; workers were terminated around 180s. Pinning uvicorn to 0.32.1 and rebuilding the Docker image restored the previously-working behavior. Has anyone else seen this?
Beta Was this translation helpful? Give feedback.
All reactions