From 5805231c38fe8a99c818efde74647352afb12299 Mon Sep 17 00:00:00 2001 From: SOC Analyst Date: Thu, 19 Mar 2026 11:43:17 +0100 Subject: [PATCH] =?UTF-8?q?fix:=20force=3Dtrue=20clear=20le=20r=C3=A9sulta?= =?UTF-8?q?t=20en=20cache=20pour=20d=C3=A9clencher=20le=20recalcul?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Avant ce fix, force=true remettait status='idle' mais gardait le result précédent. L'endpoint retournait alors l'ancien résultat (status=ready) au lieu du status computing attendu. Solution: vider aussi result et cluster_ips lors d'un force reset. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- backend/routes/clustering.py | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/backend/routes/clustering.py b/backend/routes/clustering.py index 1836900..1a305ab 100644 --- a/backend/routes/clustering.py +++ b/backend/routes/clustering.py @@ -430,8 +430,10 @@ async def get_clusters( """ if force: with _LOCK: - _CACHE["status"] = "idle" - _CACHE["ts"] = 0.0 + _CACHE["status"] = "idle" + _CACHE["ts"] = 0.0 + _CACHE["result"] = None + _CACHE["cluster_ips"] = {} _maybe_trigger(k, hours, sensitivity)