I do not think it is even getting to the point where I can accept the connection from within the consumers.py....and 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 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 somehow > driven by my setup..although any suggestions are welcome! > > My setup: > app1/ > ...AsyncWebsocketConsumer (consumers.py) > ...AsyncConsumer (backgroundTask.py) > ..a couple other function files that call the get_channel_layer to send to > a group > app2/ > ...same idea > > On Saturday, September 1, 2018 at 9:40:10 AM UTC-4, Marius Räsener wrote: >> >> 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 best practices? No Idea if >> that’s worth mentioning or already clear but to be sure... >> >> Good luck > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/945d172f-d505-4175-90e1-c4ccc5c53a9d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
