Yup, I'm seeing if we can get asgiref fixed today, otherwise I'll revert the
change that broke Django and issue 3.2.9.
Andrew
On Tue, Jun 16, 2020, at 2:48 AM, Florian Apolloner wrote:
> Ok, so rebasing PRs to current master will fix this (leaving this here as
> note for others who run into
Ok, so rebasing PRs to current master will fix this (leaving this here as
note for others who run into this).
On Tuesday, June 16, 2020 at 10:39:13 AM UTC+2, Mariusz Felisiak wrote:
>
> It's an issue with the asgiref==3.2.8, see
> https://github.com/django/asgiref/issues/170. We temporarily
It's an issue with the asgiref==3.2.8, see
https://github.com/django/asgiref/issues/170. We temporarily pinned
asgiref==3.2.7 [1].
Best,
Mariusz
[1]
https://github.com/django/django/commit/dcb4d79ef719d824431a8b3ff8ada879bbab21cc
--
You received this message because you are subscribed to
Hi,
do we have any idea what is happening on
https://djangoci.com/job/pr-mariadb/database=mysql,label=mariadb,python=python3.8/6459/
? It seems as if (mostly) the same set of tests is failing over and over.
Is this ASGI/concurrency related?
Cheers,
Florian
--
You received this message
