-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Daphne server does not spin up automatically with channels=4.x #1068
Comments
According to the django channel 4.0.0 release notes, daphne is now decoupled from channels. If users want to run daphne with runserver, then daphne must be added to the installed apps explicitly in the settings.
|
I've been playing around with this for
This is a pretty easy fix if you have access to the I'm planning to test adding |
On a related note, since However, when I try to install an unpinned version of
Which is a bit strange since
By specifying
Trying to force
This appears to be a bug in the conda packaging since the install_requires =
Django>=4.2
asgiref>=3.6.0,<4 |
The mismatch in how conda resolves the versions should be fixed with: conda-forge/channels-feedstock#17 and |
Describe the bug
When using a consumer class is used to create a websocket, the daphne server does not spin up on the "tethys manage start" command and therefore a websocket is never created. The outputs from the "tethys manage start" command show "Starting development server at http://127.0.0.1:8000/"
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect a daphne server to spin up and have a message like "Starting ASGI/Daphne version 4.1.2 development server at http://127.0.0.1:8000/".
Tethys Environment Information
channels=4.x
The text was updated successfully, but these errors were encountered: