Control: forwarded -1 https://github.com/django/channels_redis/issues/332 Control: tags -1 fixed-upstream Control: fixed -1 4.1.0-1
On Fri, Dec 30, 2022 at 08:39:40PM +0100, Jérémy Lal wrote: > multiple python applications using channels-redis 4.0.0 have that issue: > https://github.com/django/channels_redis/issues/332 > > It doesn't look like it's going to be fixed soon. > It might be a good idea to not ship channels-redis 4.0.0 in bookworm. I ran into this too just now, and it was very confusing. I was able to work around it by switching to RedisPubSubChannelLayer, but I'm not totally sure that's a good idea: it's still marked as being in beta even now, 4.0.0's RedisPubSubChannelLayer also suffers from https://github.com/django/channels_redis/issues/343, and in my application the switch provoked some kind of extremely weird coverage failure, possibly https://github.com/python/cpython/issues/106749. Since there is now an upstream fix (https://github.com/django/channels_redis/pull/347), I think it would be worth backporting this to bookworm. -- Colin Watson (he/him) [cjwat...@debian.org]
