How does set_user work with concurrency with FastAPI

[Exagone313]

Hello,

Is set_user concurrency-safe? FastAPI uses an event loop and (if I understand correctly) the processing of a response can be stopped and resumed while another route is handled in the middle. This means that, when the first route processing is resumed, the currently set user may not be the one set previously.

Or, does sentry-sdk deal with this and saves the user per-request somehow?

Thanks.

[niqodea]

I tested this locally and it appears to work as expected—the user is reset with each new request. However, I'm not confident this guarantees the same behavior in a production environment. A clarification on this would be helpful!