Hi,
I'm coming back with this one as well. I managed to fix my problem. In my
consumer, I was making normal Django database queries without the
@database_sync_to_async decorator.
As soon as I started wrapping my code properly with this decorator,
everything started to work fine. See below.
I've just had trouble with exactly the same error. In my case I was
building from the tutorial ChatConsumer with my own XChatConsumer and I
hadn't referenced it in the routing.py. As a result the tutorial async chat
consumer was receiving a scope that did not contain a room_name in its
url_rout
Hi Simon,
Sorry to hear that you are having the same problem! Channels can be a
blessing and a curse. I find it very finicky with very poor documentation &
poor error handling. As for the fix: I had an AsyncWebsocketConsumer class
in consumers.py within which I had a custom __init__ function. I
Hi itsnate_b,
Would you mind elaborating on your fix?
I'm getting this exact error and I'm at a complete loss. Everything works
fine in local, but on my live server, after a couple of minutes/hours of
working fine, I start getting this error in the logs.
Thanks!
Le dimanche 2 septembre 2018
Turns out there was an erroneous *init* function in the
AsyncWebsocketConsumer class. Removing it fixed the issue.
On Saturday, September 1, 2018 at 1:23:10 PM UTC-4, itsnate_b wrote:
>
> I do not think it is even getting to the point where I can accept the
> connection from within the consumers
I do not think it is even getting to the point where I can accept the
connection from within the consumers.pyand I'm not sure how to get a
better traceback than the one I already provided.
On Saturday, September 1, 2018 at 1:20:16 PM UTC-4, itsnate_b wrote:
>
>
> Hi Marius,
> Thanks for the
Hi Marius,
Thanks for the recommendation. Yes, I am using channel layers outside of
consumers, however, this has not been an issue in the past. I am not clear
on what you mean by "virtualenv best practices"? Yes, this is running in a
venv, and it has worked in the past. I do think this issue is
Hey, my guess is to check redis integration, f.e. like mentioned here at the
bottom (outside of consumers):
https://channels.readthedocs.io/en/latest/topics/channel_layers.html
next guess, since an unintended lock feels rather basic to me is to make sure
you‘re still following the virtualenv bes
I have the latest Django (2x), channels (2x), and redis/docker as of Aug
31st, 2018 installed. I am encountering a django channels error and have no
idea why this is happening...has anyone seen this output? What is the
potential cause? Feeling pretty stuck with the error below...happens when
re
9 matches
Mail list logo
