-
Notifications
You must be signed in to change notification settings - Fork 197
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
RedisChannelLayer.receive runs forever #44
Comments
This should fix django#44. Hope it does not break anything else.
The ASGI spec says "block means that the call can take as long as it likes", so this is valid behaviour. What needs fixing here is the channels Worker; if you could file a bug against the |
@andrewgodwin: Done. |
@andrewgodwin maybe the ASGI spec should be reworded, because in the same paragraph there is the sentence: "If block is True, then it will not return until after a built-in timeout or a message arrives;" |
Yes, I will clarify that paragraph so it's clear it is allowed to block forever. |
RedisChannelLayer.receive
, that was reworked in #43, now hangs forever if called with block. That was not the case in the previous version (it returned(None, None)
. This prevents channelsWorker
from exiting if termed is set to true (e.g. in the signal handler).The text was updated successfully, but these errors were encountered: