Early init chat_history in chat api to avoid unbound in edge case

Monitor disconnect can trigger earlier than chat history is
initialized. This can cause unbound chat history exception.
This commit is contained in:
Debanjum
2025-07-06 12:03:43 -07:00
parent 8cd2a1a961
commit b27ba1d24b

View File

@@ -22,7 +22,7 @@ from khoj.database.adapters import (
PublicConversationAdapters, PublicConversationAdapters,
aget_user_name, aget_user_name,
) )
from khoj.database.models import Agent, KhojUser from khoj.database.models import Agent, ChatMessageModel, KhojUser
from khoj.processor.conversation import prompts from khoj.processor.conversation import prompts
from khoj.processor.conversation.openai.utils import is_local_api from khoj.processor.conversation.openai.utils import is_local_api
from khoj.processor.conversation.prompts import help_message, no_entries_found from khoj.processor.conversation.prompts import help_message, no_entries_found
@@ -739,6 +739,7 @@ async def chat(
generated_mermaidjs_diagram: str = None generated_mermaidjs_diagram: str = None
generated_asset_results: Dict = dict() generated_asset_results: Dict = dict()
program_execution_context: List[str] = [] program_execution_context: List[str] = []
chat_history: List[ChatMessageModel] = []
# Create a task to monitor for disconnections # Create a task to monitor for disconnections
disconnect_monitor_task = None disconnect_monitor_task = None