From 1a883b421f6c22b9dc896f489ea138e650182b71 Mon Sep 17 00:00:00 2001 From: Teknium <127238744+teknium1@users.noreply.github.com> Date: Mon, 18 May 2026 21:27:58 -0700 Subject: [PATCH] fix(kanban): remove orphan conflict markers from config.py (#28458) PR #28452 (salvage of #23790, stale detection) merged with leftover git conflict markers in hermes_cli/config.py around the `dispatch_stale_timeout_seconds` config block, breaking config import and any code path that loads it. Cleans up the markers and keeps both config blocks (worker log rotation/orchestrator + stale detection). Resolves a self-introduced regression. --- hermes_cli/config.py | 3 --- 1 file changed, 3 deletions(-) diff --git a/hermes_cli/config.py b/hermes_cli/config.py index c48ec10db00..9c4197c80fb 100644 --- a/hermes_cli/config.py +++ b/hermes_cli/config.py @@ -1530,7 +1530,6 @@ DEFAULT_CONFIG = { # same task/profile (spawn_failed, timed_out, or crashed). Reassignment # resets the streak for the new profile. "failure_limit": 2, -<<<<<<< HEAD # Worker stdout/stderr logs rotate at spawn time. Defaults preserve # the historical 2 MiB + one-backup behavior; long-running workers can # raise these to keep more early failure evidence. @@ -1555,14 +1554,12 @@ DEFAULT_CONFIG = { # large bulk-load of triage tasks from spending a burst of aux # LLM calls in one tick. Excess tasks defer to the next tick. "auto_decompose_per_tick": 3, -======= # Stale detection: running tasks that have exceeded this many # seconds without a heartbeat (since ``last_heartbeat_at``) are # auto-reclaimed to ``ready`` on the next dispatcher tick. The # worker process (if still running host-locally) is terminated # before the reclaim. 0 disables stale detection entirely. "dispatch_stale_timeout_seconds": 14400, ->>>>>>> 0b6d673e7 (feat(kanban): stale detection for running tasks in dispatcher) }, # execute_code settings — controls the tool used for programmatic tool calls.