Channels 2: Consumer running twice when two users simultaneously share socket

I am running into an issue using Channels where if two users are connected to the same socket, the consumer will run twice. When a single user is connected, only once. So in practice: when I have two users chatting with each other over channels, a single sent message will be run through the co

Re: Channels 2: Consumer running twice when two users simultaneously share socket

Andrew Godwin wrote: > > Can you clarify what you mean by "two users connected to the same socket"? > If you have two websockets connected, you'll have two copies of your > consumer running, one for each socket. > > Andrew > > On Thu, Mar 1, 2018 at 7:52 AM, l

Re: Channels 2: Consumer running twice when two users simultaneously share socket

;chat.message" to the group, that means everything in the group is going to > receive the message, run that handler, and save (so with 2 connected you > get 2 saves, etc.) > > I'd recommend saving instead where you send to the group. > > Andrew > > On Thu, Mar 1, 201

Django sending syntax errors on ES syntax of imported JS file

I'm attempting to use the script of a third party JS library: {% block javascript %} ...{% endblock javascript %} Doing so will return an error: `Uncaught SyntaxError: Enexpected token {` And this error refers to line 1 of 'typed.js', more specifically, this line of JS code: `imp

Geo-Django on Heroku throwing "No such file": libjasper.so.1

Heroku-16, Django==1.11.8 Any `heroku run python manage.py x` command will throw: OSError: libjasper.so.1: cannot open shared object file: No such file or directory According to this issue here: https://github.com/cyberdelia/heroku-geo-buildpack/issues/43, heroku-16 is without libjasper a

Re: Sample of GeoDjanco websites

Hi Jani. I wonder if you've ever had to push any geo-django involved apps to heroku's servers. I'm attempting this now and running into issues regarding libjasper.so.1. The community and documentation around geodjango seems quite thin.. On Tuesday, March 20, 2018 at 4:12:04 PM UTC+9, Jani Ti

Daphne server on Heroku will not allow app to start

The dockerized app successfully uploads and the code is hosted on Heroku's docker container registry. I can shell inside, run `python manage.py migrate` or `./manage.py runserver`, etc. So the chokepoint likely seems to be the daphne command I'm running. `web: daphne config.asgi:application

Does Daphne of Django Channels send out a heartbeat to keep the connection alive?

Is this even done server side? Or does it need to be implemented with js for the client? I ask because it appears that my connection repeatedly before or during the attempt to connect. It only happens when uploaded to Heroku's servers as well. -- You received this message because yo