-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
add support for eventlets _AlreadyHandled object #1406
Conversation
…ect has no attribute status_code
Does this just silence the error? |
thanks for the patch.
but such changes must be done in the eventlet worker code since it's
specific to it.
What about catching an optional value set by the worker?
btw Wondering why the lib can't use the gunicorn way that provide a
consistent behaviour across worker and doesn't force the usage of eventlet
though...has it been discussed?
…On Wed, 7 Dec 2016 at 01:40, Hum4n01d ***@***.***> wrote:
Does this just silence the error?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1406 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAA4ov3bjhcd96nALnar1RhT_bVI4gluks5rFgCYgaJpZM4LFhXG>
.
|
@Hum4n01d The error was caused by an empty wsgi response on disconnect, due to a slightly different implementation of the _AlreadyHandled object. The goal of _AlreadyHandled is to raise a StopIteration exception to close the socket. |
I don't totally get what you're saying but please merge it @benoitc |
@stefaang the change can be simpler imo, so we check Instead we could check it using a function |
You're right, that's a better approach. I'll get around with another fix. |
So can it be merged? |
This looks good to me. |
merged. Thanks! |
Yay! Now my logs won't be clogged up |
Thank you for this fix <3 |
add support for eventlets _AlreadyHandled - issue 1210 - Response object has no attribute status_code
fixes #1210