We updated the GUNICORN_TIMEOUT value in the application configuration in PR 416, but the timeout behavior remains unchanged.
This suggests that the value defined in the config is not being loaded correctly, and the application is instead falling back to the default timeout defined in the code (120 seconds). We "fixed" this with this workaround in #418 but this is not the real fix, it is just a workaround.
The application should read and apply the GUNICORN_TIMEOUT value defined in the configuration.
The configured timeout should override the default value.
We updated the
GUNICORN_TIMEOUTvalue in the application configuration in PR 416, but the timeout behavior remains unchanged.This suggests that the value defined in the config is not being loaded correctly, and the application is instead falling back to the default timeout defined in the code (120 seconds). We "fixed" this with this workaround in #418 but this is not the real fix, it is just a workaround.
The application should read and apply the GUNICORN_TIMEOUT value defined in the configuration.
The configured timeout should override the default value.