From d8bf80c6d1ccf1079c38cfbb097497fb602d2c1d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tom=C3=A1s=20Badenes?= Date: Sun, 16 Aug 2026 12:28:42 -0300 Subject: [PATCH] fix: lowercase mission status "error" to match the platform The platform matches mission status literals exactly, including case: "OK" | "warning" | "error". MISSION_STATUS_ERROR published "Error", which matches nothing, so executor missions that failed never got error status treatment. The MiR and Gausium connectors each define their own lowercase literals to work around this. Adds MISSION_STATUS_WARNING to complete the vocabulary. Co-Authored-By: Claude Fable 5 --- inorbit_edge/missions.py | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/inorbit_edge/missions.py b/inorbit_edge/missions.py index 9f5c0ee..cd71a05 100644 --- a/inorbit_edge/missions.py +++ b/inorbit_edge/missions.py @@ -31,9 +31,11 @@ MISSION_STATE_COMPLETED = "Completed" MISSION_STATE_CANCELED = "Canceled" -# Mission status +# Mission status. The platform matches these exactly, including case: +# "OK" | "warning" | "error". MISSION_STATUS_OK = "OK" -MISSION_STATUS_ERROR = "Error" +MISSION_STATUS_WARNING = "warning" +MISSION_STATUS_ERROR = "error" class MissionsModule: