> Channels websocket takes down the client one, but maybe they are both made
> to crash by some third, external, force?
>
> Andrew
>
> On Sun, Jun 17, 2018 at 11:33 AM Nathan Bluvol > wrote:
>
>> I am using Django 2.0.5, Python 3.6.2, Django Channels 2.1.1, aiohttp
&
I am using Django 2.0.5, Python 3.6.2, Django Channels 2.1.1, aiohttp 3.1.3.
Background:
I am connecting to an external websocket, asynchronously, using aiohttp
within a background channels worker. Once triggered, the socket connection
stays alive, listening/streaming, and sends incoming message
I am using Django 2.0.5, channels 2.1.1, aiohttp 3.1.3
two issues: (1) everything works for a while and then the channels
websocket dies. Error is 'No handler for message type...'. (2) the
background `await t1` call appears to be blocking and it appears that any
attempt to trigger closeConnect
3 matches
Mail list logo