raise ValueError("No handler for message type %s" % message["type"])
No handler for message type backgroundWorkerUpdate
On Monday, June 18, 2018 at 9:33:12 AM UTC-4, itsnate_b wrote:
>
> Hi Andrew,
> Thank you for your quick reply. I use AsyncConsumer in the backgrou
tch(result)
File "...lib/python3.6/site-packages/channels/consumer.py", line 69, in
dispatch
raise ValueError("No handler for message type %s" % message["type"])
No handler for message type backgroundWorkerUpdate
On Monday, June 18, 2018 at 9:33:12 AM UTC-4,
I'm assuming you already did this?
django-admin startproject mysite
If so, then you should have a mysite folder, inside of another mysite
folder. Inside of there you should have views.py, models.py. You may need
to create the urls.py file, if it's not already there.
should look like what is sh
No problem. Good luck!
On Monday, June 18, 2018 at 12:46:23 PM UTC-4, Django starter wrote:
>
> Hi Nathan,
>
> Appreciate your response, it wasnt there,
>
> I would create it again and check and thanks a lot for responding
>
> On Mon, Jun 18, 2018 at 11:43 PM, itsn
here
On Monday, June 18, 2018 at 12:05:26 PM UTC-4, itsnate_b wrote:
>
> Further to the message above - I moved everything into the consumers.py
> file and routed to the class inside of there. Still getting this error
> AFTER I get the print statement
> print('awai
kground worker versus the current channels
implementation of initializing a new class for every routing call. Will
post under a separate issue.
On Monday, June 18, 2018 at 2:27:57 PM UTC-4, itsnate_b wrote:
>
> I am unable to determine the cause of the handler issue (assuming
>
I am using Django 2.0.5, Python 3.6.2, Django Channels 2.1.1, aiohttp 3.1.3.
I have created a background worker class which is initialized on a route to
the appropriate event/function. Problem is that it initializes a *new*
instance of the class on every triggered call, meaning that I cannot acc
__pycache__
> │ │ │ ├── __init__.cpython-36.pyc
> │ │ │ ├── settings.cpython-36.pyc
> │ │ │ ├── urls.cpython-36.pyc
> │ │ │ └── wsgi.cpython-36.pyc
> │ │ ├── settings.py
> │ │ ├── urls.py
> │ │ └── wsgi.py
> │ └── manage.py
>
>
> Could you please help me kn
Post some code please and I can try to help.
On Tuesday, June 19, 2018 at 11:21:31 AM UTC-4, ILia Hopa wrote:
>
> hello! is it possible to set the handler of the group message in the
> different consumer (from the one from which message was dispatched).
>
> ex: I have 2 consumers: `cli0consumer`
can you please show what's in your routing.py? How are you routing to
command_status_all?
On Tuesday, June 19, 2018 at 4:01:32 PM UTC-4, ILia Hopa wrote:
>
> Here, relevant code:
> Want a clients connected to Cli0Consumer to receive a message.
>
> class Cli0Consumer(JsonWebsocketConsumer):
>
quot;, line 219, in
> _call_with_frames_removed
> File "/home/ssyed/polls/bin/mysite/mysite/urls.py", line 20, in
> path('polls/', include('polls.urls')),
> NameError: name 'include' is not defined
>
>
>
> *TREE STRUCTURE : *
>
gt;
> On Tue, Jun 19, 2018 at 6:45 AM itsnate_b > wrote:
>
>> I am using Django 2.0.5, Python 3.6.2, Django Channels 2.1.1, aiohttp
>> 3.1.3.
>>
>> I have created a background worker class which is initialized on a route
>> to the appropriate event/function.
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
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
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,
&g
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 w
e.
Hope that helps.
Cheers,
Nathan
On Tuesday, October 9, 2018 at 9:59:33 AM UTC-4, Simon Vézina wrote:
>
> 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, b
17 matches
Mail list logo
