Re: Django 2.0 and AsgiRequest Error

All: Yes, this is was identical to GitHub: https://github.com/django/channels/issues/981. Upgrading to MIDDLEWARE from MIDDLEWARE_CLASSES solved the problem. G Broten On Wednesday, March 21, 2018 at 8:54:47 AM UTC-6, G Broten wrote: > > Andrew: > No, issue 981 wasn't posted by

Re: Django 2.0 and AsgiRequest Error

Andrew: No, issue 981 wasn't posted by me, but I too am using MIDDLEWARE_CLASSES so this is most likely the same issue. I'm looking into it. Thanks, G Broten On Tuesday, March 20, 2018 at 4:05:07 PM UTC-6, Andrew Godwin wrote: > > Hi - did you also open this issue on

Django 2.0 and AsgiRequest Error

.0) redis (2.10.6) requests (2.11.1) setuptools (28.8.0) six (1.11.0) tornado (4.5.3) Twisted (17.9.0) txaio (2.9.0) vcrpy (1.11.1) vine (1.1.4) wrapt (1.10.11) yarl (1.1.1) zope.interface (4.4.3) Thanks in advance. G Broten -- You received this message because you are subscribed to the Googl

Re: Django 2.0.2, Channels 2.0.2 and Celery 4.1 Issue

else using Channels 2.0 with Celery will find this thread of use. G Broten On Friday, March 2, 2018 at 12:57:01 PM UTC-6, Ken Whitesell wrote: > > Taking a stab at this - I believe the original problem may be here: > channel_layer.group_send( > settings.CHANNEL_GROUP,

Django 2.0.2, Channels 2.0.2 and Celery 4.1 Issue

t;text": "Hello World"}, ) This results in the following runtime warning and the Celery task fails to run (the debug message is never printed) : [2018-03-02 09:45:19,804: WARNING/ForkPoolWorker-2] /home/broteng/.pyenv/versions/3.6.3/envs/djchannels2/lib/python3.6/site-packages/bil