Leaklens

django__django-13344

Coroutine passed to the first middleware's process_response() instead of HttpResponse.

Verdict: the issue points to the file or function that was changed (Tier B).

I think it's a bug in SecurityMiddleware : its __init__ does not call super().__init__(). This causes MiddlewareMixin._async_check() to not be called during init and the _is_coroutine magic attribute to be missing despite the async_capable=True declaration.

The two checks disagreed (stated fix vs. points to it); the lower reading shown: “I think it's a bug in SecurityMiddleware : its __init__ does not call super().__init__(). This causes MiddlewareMixin._async_check() to not be called…”

All SWE-bench Verified tasks · more django/django tasks · How the check works