runserver and daphne gives error after upgrade about channels

[andrewgodwin]

Oh, yes! I've fixed that in fe35254.

The "multiple response messages" problem turned out to be an issue with the database backend duplicating messages, the new version now uses transactions to stop that - so I'm closing this, since I think these are both fixed. Reopen if it's not.

[andrewgodwin]

What version of Django, channels, Daphne, asgiref are you using, and what's your channel layer setting look like?

[rajasimon]

Pip freeze

Django==1.9.2
Twisted==15.5.0
argparse==1.2.1
asgiref==0.9
autobahn==0.12.1
channels==0.9.1
daphne==0.9
psycopg2==2.6.1
pytz==2015.7
six==1.10.0
txaio==2.2.1
wsgiref==0.1.2
zope.interface==4.1.3

And my channel layer settings look like this ...

# In settings.py
CHANNEL_LAYERS = {
    "default": {
        "BACKEND": "channels.database_layer.DatabaseChannelLayer",
        "ROUTING": "buildsys.routing.channel_routing",
    },
}

[rajasimon]

I don't know why but looks like " Got multiple Response messages " not coming right now when running runserver ...

And changing asgi.py line_numer : 83 django.setup(set_prefix=False) this to django.setup() will work..and I got connected message in my chrome console. But in my terminal I got this

IntegrityError: null value in column "expiry" violates not-null constraint
DETAIL:  Failing row contains (1243, chat, !websocket.send.kfVqXOSu, null).

[andrewgodwin]

You shouldn't need django.setup in ASGI.py - where in the docs did I put that? I should fix it.

And for the database, delete your channels tables; the schema changed a bit since the earlier version, and I didn't do migrations since the user base was very low then.

[rajasimon]

No actually I was saying that In the fresh installation without editing that 83 line it throws error by default.