#31928: Coroutine passed to the first middleware's process_response() instead of
HttpResponse.
----------------------------------+------------------------------------
Reporter: Kordian Kowalski | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 3.1
Severity: Release blocker | Resolution:
Keywords: async asgi | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by Carlton Gibson):
Hi Kevin.
> would you prefer a common PR with all middlewares fixed or should I make
a separate PR for the cache ?
It’s a single issue no, a single PR, should be fine. (We can maybe do
three commits if that seems better, but it’s a single issue no? :)
I didn’t dig in yet, so you’re ahead of me but, if you can narrow down the
issue in a test case (or three...) then that’s the main thing I’d think.
Thanks for the input! Super. 👌
--
Ticket URL: <https://code.djangoproject.com/ticket/31928#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/074.288dfe9626ea3ad1709c7b04ec8e24cf%40djangoproject.com.
