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
Thank you for the cosmosdb chat history feature.
I rely on the session_state variable to keep the backend informed about earlier calls. Session_state is the only data that travels through the call chain to run_until_final_call() where I do some extra work which needs status set by my previous calls.
To minimise collision surface with other features I kept my state in a separate key within session_state: session_state['be_messages']
Would you consider using a dict key like session_state['chat_history_id'] instead of session_state to allow the state of multiple features to coexist ?
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
-
Hi @fujita-h ,
Thank you for the cosmosdb chat history feature.
I rely on the session_state variable to keep the backend informed about earlier calls. Session_state is the only data that travels through the call chain to run_until_final_call() where I do some extra work which needs status set by my previous calls.
To minimise collision surface with other features I kept my state in a separate key within session_state:
session_state['be_messages']
Would you consider using a dict key like
session_state['chat_history_id']
instead of session_state to allow the state of multiple features to coexist ?azure-search-openai-demo/app/backend/app.py
Line 230 in d277675
Related: #2303 (comment)
Thank you
Beta Was this translation helpful? Give feedback.
All reactions