chore: disable DriveMonitor temporarily for WebSocket/LLM testing
All checks were successful
BotServer CI/CD / build (push) Successful in 7m30s

DriveMonitor polling may be consuming resources and interfering with
LLM response delivery. Disabling to isolate the chat pipeline.

Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
This commit is contained in:
Rodrigo Rodriguez (Pragmatismo) 2026-04-14 09:18:49 -03:00
parent 3159d04414
commit 251ee9e106

View file

@ -890,8 +890,8 @@ pub async fn start_background_services(
trace!("ensure_llama_servers_running completed");
}
#[cfg(feature = "drive")]
start_drive_monitors(app_state.clone(), pool).await;
// DISABLED: DriveMonitor for testing WebSocket/LLM response in isolation
// start_drive_monitors(app_state.clone(), pool).await;
// Local file monitoring removed - Drive (MinIO) is the only source now
// #[cfg(feature = "local-files")]