From 5db0d72c909ac909054e1c175f5b53cf595e6919 Mon Sep 17 00:00:00 2001 From: sprmn24 <164800352+sprmn24@users.noreply.github.com> Date: Mon, 18 May 2026 20:16:08 -0700 Subject: [PATCH] fix(kanban): use 'is not None' check for max_runtime_seconds in create_task max_runtime_seconds=0 was being silently coerced to None due to a falsy check (if max_runtime_seconds). Zero is a valid value that causes the dispatcher to immediately time out a task. The adjacent max_retries parameter already used the correct 'is not None' pattern. Fixes the inconsistency by aligning max_runtime_seconds with max_retries. --- hermes_cli/kanban_db.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hermes_cli/kanban_db.py b/hermes_cli/kanban_db.py index 00f8e14dbf3..ce7f7a8d8c8 100644 --- a/hermes_cli/kanban_db.py +++ b/hermes_cli/kanban_db.py @@ -1408,7 +1408,7 @@ def create_task( workspace_path, tenant, idempotency_key, - int(max_runtime_seconds) if max_runtime_seconds else None, + int(max_runtime_seconds) if max_runtime_seconds is not None else None, json.dumps(skills_list) if skills_list is not None else None, int(max_retries) if max_retries is not None else None, ),