-
Notifications
You must be signed in to change notification settings - Fork 321
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
Upgrading to gunicorn >19.4.1 causes server to crash #204
Comments
The --no-sendfile option had a confusing entry in the usage message. Even though sendfile is enabled by default, the --no-sendfile flag showed a true value as the default, which could be interpreted to mean that by default sendfile support is disabled. This change makes the default "None", meaning sendfile is not disabled, which is hopefully slightly more clear. Close #1156
@kevgliss I think you just need to pass along |
Sorry, that's |
@tilgovi That didn't seem to help. Stacktrace without klass.const:
With your suggestion:
I am thinking that this has more to do with Flask-Script implementation more than anything else. It's weird because |
@kevgliss it seems like the the options = (
Option(
*klass.cli,
action=klass.action,
**({'const': klass.const} if klass.const is not None else {})
) for setting, klass in settings.iteritems() if klass.cli
) |
Pin google-api-core to 1.31.0
There is currently an issue with how argparse is handling an upstream change in gunicorn.
Here https://github.com/Netflix/lemur/blob/master/lemur/manage.py#L387 we take the settings generated by gunicorn and combine them with our own options.
If we take a look at the difference between the two versions:
19.4.1
19.4.4
The only change I make out is the change from
['--no-sendfile'] store_false
to['--no-sendfile'] store_const
. This change corresponds with this change:benoitc/gunicorn@d8b6f0a#commitcomment-15256412
The text was updated successfully, but these errors were encountered: