Move pairing cache repair into planning flow

This commit is contained in:
2026-04-15 08:06:15 +08:00
parent 608c4ce257
commit 572c454a8e
8 changed files with 412 additions and 7 deletions
+2
View File
@@ -218,6 +218,8 @@ async def find_pairs_endpoint(
except Exception as e:
if isinstance(e, HTTPException):
raise e
if isinstance(e, RuntimeError):
raise HTTPException(status_code=409, detail=str(e))
logger.exception("处理 AOI 或查找干涉对时发生错误")
raise HTTPException(status_code=500, detail="处理 AOI 或查找干涉对时发生错误,请查看后端日志")
+2 -2
View File
@@ -74,12 +74,12 @@ class SpatialService:
if cache_status in {"FAILED", "UNINITIALIZED", "ERROR"} or (scene_count > 1 and pair_count == 0):
raise RuntimeError(
"配对候选缓存当前不可用,请先在系统自检中执行“全量重建配对缓存”或“增量修复”。"
"配对候选缓存当前不可用,请先在生产规划页执行“修复配对基础”或“强制全量重建”。"
)
if degraded:
warnings.append(
f"配对候选缓存当前状态为 {cache_status},本次结果基于现有缓存生成,建议尽快执行增量修复或全量重建"
f"配对候选缓存当前状态为 {cache_status},本次结果基于现有缓存生成,建议尽快在生产规划页执行缓存修复"
)
candidate_pool = await self._query_pairing_metric_cache(