Intended behavior on BackgroundTasks about starlette-context HOT 2 CLOSED

I haven't been using any asgi for over a year now but if I had to guess - background tasks are not as background as it seems. They still run within the request-response cycle. They are initialized just after the response has been sent (asynchronously). It's the same event loop, so "the context of the context" will be available. If one of these tasks was doing some computation ( or time.sleep(5)) your worker would be blocked as its event loop would be blocked.

https://github.com/encode/starlette/blob/881af38cc2e038de1f02e4fba7b7dab2df79b38a/starlette/responses.py#L148-L159

If I understand it correctly, response.__call__ is exactly what self.app(scope, receive, send_wrapper) is doing, so the context hasn't been reset yet.

So yeah, although surprising, it makes sense.

from starlette-context.

ooh, I see. The background task is processed right after, literally the next line after the response is sent, which as seen from the middleware, is still in the try block. the reset is only after, in the finally block, which ends up executed after the response AND the background task.
I understand now, and feel I can sleep soundly again.

from starlette-context.