fix(chat): resolve Auto-route failover event-loop freeze (#812)
Root cause: ensure_structured_column() executed a synchronous blocking engine.connect().execute(SELECT information_schema.columns ...) inside the async request path (_build_chat_history / _maybe_compress_history), freezing the uvicorn event loop and hanging all endpoints (~200s, recovered only by docker restart). Fix: - chat_context.py: remove per-request ensure_structured_column() calls; run once idempotently at app startup (main.py lifespan). Use CURRENT_DATABASE() for PostgreSQL compatibility. - main.py: add startup-only ensure_structured_column() hook (try/except). - llm_client.py: trust_env=False + bounded httpx.Timeout/wait_for so broken endpoints fail fast instead of hanging the event loop. - chat_service.py: run media generation in a background daemon thread with its own event loop (_launch_media_task_bg) so SSE end does not cancel image/video tasks (#811); remove TEMP faulthandler diagnostic. Safe-align: persist accumulated live container changes (admin/*, knowledge, market, models, config, observability, mcp_client, platform_knowledge, im_bot_platform, chat_media, capability_registry, requirements) and add workflow_templates. Verified: live failover test (model-006 -> conn-refused) returns in ~1.9s with concurrent login 0.83s/200; event-loop responsiveness restored (sub-second).
This commit is contained in:
1 parent
394a7786e0
commit
a2504bce34
27 files changed
+253
-59
No files matched your search
@@ -0,0 +1,35 @@
|
||||
version: "1.0"
|
||||
name: "Code Review Pipeline"
|
||||
description: "Generate code → review → merge. A standard code-review workflow."
|
||||
category: development
|
||||
|
||||
nodes:
|
||||
- id: code_gen
|
||||
type: llm
|
||||
description: "Generate code based on requirements"
|
||||
on_error: halt
|
||||
config:
|
||||
model: auto
|
||||
system_prompt: "You are a senior software engineer. Write clean, production-ready code based on the user's requirements. Include comments and error handling."
|
||||
|
||||
- id: review
|
||||
type: llm
|
||||
description: "Review generated code for bugs and style"
|
||||
on_error: continue
|
||||
config:
|
||||
model: auto
|
||||
system_prompt: "You are a code reviewer. Analyze the provided code for bugs, style issues, performance problems, and security vulnerabilities. Provide specific, actionable feedback."
|
||||
|
||||
- id: merge
|
||||
type: reduce
|
||||
description: "Combine code with review feedback"
|
||||
config:
|
||||
strategy: concat
|
||||
|
||||
edges:
|
||||
- from: code_gen
|
||||
to: review
|
||||
- from: code_gen
|
||||
to: merge
|
||||
- from: review
|
||||
to: merge
|
||||
@@ -0,0 +1,35 @@
|
||||
version: "1.0"
|
||||
name: "Multi-Agent Debate"
|
||||
description: "Two agents debate a topic from opposing perspectives, then a judge agent synthesizes the conclusion."
|
||||
category: creativity
|
||||
|
||||
nodes:
|
||||
- id: proponent
|
||||
type: llm
|
||||
description: "Argue in favor of the proposition"
|
||||
on_error: continue
|
||||
config:
|
||||
model: auto
|
||||
system_prompt: "You are a skilled debater. Argue strongly IN FAVOR of the given proposition. Use logic, evidence, and persuasive reasoning. Be passionate but fair."
|
||||
|
||||
- id: opponent
|
||||
type: llm
|
||||
description: "Argue against the proposition"
|
||||
on_error: continue
|
||||
config:
|
||||
model: auto
|
||||
system_prompt: "You are a skilled debater. Argue strongly AGAINST the given proposition. Use logic, evidence, and persuasive reasoning to find flaws in the proponent's case."
|
||||
|
||||
- id: judge
|
||||
type: llm
|
||||
description: "Evaluate both sides and reach a conclusion"
|
||||
on_error: continue
|
||||
config:
|
||||
model: auto
|
||||
system_prompt: "You are an impartial judge. Evaluate both arguments fairly. Identify the strongest points from each side. Provide a balanced conclusion and recommendation."
|
||||
|
||||
edges:
|
||||
- from: proponent
|
||||
to: judge
|
||||
- from: opponent
|
||||
to: judge
|
||||
@@ -0,0 +1,25 @@
|
||||
version: "1.0"
|
||||
name: "RAG Search Pipeline"
|
||||
description: "Search knowledge base → augment with context → generate answer. Standard RAG pipeline."
|
||||
category: productivity
|
||||
|
||||
nodes:
|
||||
- id: search
|
||||
type: llm
|
||||
description: "Generate search queries and retrieve relevant context"
|
||||
on_error: continue
|
||||
config:
|
||||
model: auto
|
||||
system_prompt: "You are a search specialist. For the given question, identify 2-3 key search points. Then search the provided knowledge base for relevant information. Return the most relevant passages with source references."
|
||||
|
||||
- id: answer
|
||||
type: llm
|
||||
description: "Generate final answer with citations"
|
||||
on_error: continue
|
||||
config:
|
||||
model: auto
|
||||
system_prompt: "You are a knowledge assistant. Using the search results provided, generate a comprehensive answer. Always cite your sources. If information is insufficient, clearly state what is missing."
|
||||
|
||||
edges:
|
||||
- from: search
|
||||
to: answer
|
||||
@@ -0,0 +1,25 @@
|
||||
version: "1.0"
|
||||
name: "Research & Answer"
|
||||
description: "Research topic → generate answer. Uses two LLM nodes for research and synthesis."
|
||||
category: productivity
|
||||
|
||||
nodes:
|
||||
- id: research
|
||||
type: llm
|
||||
description: "Search and gather information on the topic"
|
||||
on_error: continue
|
||||
config:
|
||||
model: auto
|
||||
system_prompt: "You are a thorough researcher. Search for key facts, data points, and relevant context about the given topic. Provide a comprehensive summary with citations."
|
||||
|
||||
- id: answer
|
||||
type: llm
|
||||
description: "Synthesize research into final answer"
|
||||
on_error: continue
|
||||
config:
|
||||
model: auto
|
||||
system_prompt: "You are a professional writer. Based on the research summary provided, craft a clear, well-structured answer for the user. Include key findings and actionable insights."
|
||||
|
||||
edges:
|
||||
- from: research
|
||||
to: answer
|
||||
Reference in new issue
Block a user