You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am calling an intensive operation in async using FastAPI to tag a bunch of content. When I go to run another script and utilize the same FastAPI endpoint, the JSON I get back is a response to the request I sent, but the payload/response shows the assistant_id used was the one I am calling for this other operation, even though I am explicitely sending the assistant_id to the FastAPI endpoint. When I discontinue my job running in the background the issue stops. This tells me that if I run multiple operatons in AsyncOpenAI concurrently, they will ultimately get confused running in concurrence. Does AsyncOpenAI client internally manages sessions in a way that isolates requests or will it re-use sessions across requests?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am calling an intensive operation in async using FastAPI to tag a bunch of content. When I go to run another script and utilize the same FastAPI endpoint, the JSON I get back is a response to the request I sent, but the payload/response shows the assistant_id used was the one I am calling for this other operation, even though I am explicitely sending the assistant_id to the FastAPI endpoint. When I discontinue my job running in the background the issue stops. This tells me that if I run multiple operatons in AsyncOpenAI concurrently, they will ultimately get confused running in concurrence. Does AsyncOpenAI client internally manages sessions in a way that isolates requests or will it re-use sessions across requests?
Beta Was this translation helpful? Give feedback.
All reactions