From d84284c8fbec305e94a6c2f6b825e8e3430d9569 Mon Sep 17 00:00:00 2001 From: TrezOne Date: Thu, 7 Aug 2025 10:46:57 -0400 Subject: [PATCH] Updating edit_monitor{) to let SWAG start even with broken monitor. --- root/app/auto_uptime_kuma/uptime_kuma_service.py | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/root/app/auto_uptime_kuma/uptime_kuma_service.py b/root/app/auto_uptime_kuma/uptime_kuma_service.py index 3c4c490..1883117 100644 --- a/root/app/auto_uptime_kuma/uptime_kuma_service.py +++ b/root/app/auto_uptime_kuma/uptime_kuma_service.py @@ -169,7 +169,13 @@ class UptimeKumaService: is actually "delete" followed by "add" so that in the end the monitors are actually recreated """ - new_monitor_data = self.build_monitor_data(container_name, monitor_data) + try: + new_monitor_data = self.build_monitor_data(container_name, monitor_data) + self.validate_monitor_data(new_monitor_data) + except Exception as e: + Log.info(f"Invalid monitor data for '{container_name}'. Skipping edit. Reason: {e}") + return + existing_monitor_data = self.get_monitor(container_name) old_content = self.config_service.read_config_content(container_name) new_content = self.config_service.build_config_content(new_monitor_data)