From 072f4702125bda61cc9557d7beb19738f5b2e5ab Mon Sep 17 00:00:00 2001 From: CleverThis Date: Thu, 16 Apr 2026 07:11:17 +0000 Subject: [PATCH] fix(agents): make bug-hunt-pool-supervisor tracking non-blocking to prevent initialization hangs The automation-tracking-manager call in step 5 was blocking the main loop indefinitely, causing 3+ consecutive initialization failures. This commit documents the fix in CHANGELOG.md with the proper issue reference. ISSUES CLOSED: #8835 --- CHANGELOG.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 595123305..5993ce47f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -28,6 +28,14 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). correctly in all deployment modes: Docker containers, local pip installs (wheel or editable), and development environments. - **TDD Non-AssertionError Guard Visibility** (#8294): `apply_tdd_inversion` in +- **bug-hunt-pool-supervisor Non-Blocking Tracking** (#8835): The automation-tracking-manager + call in step 5 was blocking the main loop indefinitely, causing 3+ consecutive initialization + failures. Step 5 now explicitly marks tracking as best-effort -- if the call does not complete + within a reasonable time or fails, it is skipped and the supervisor continues to the next + cycle. A new Rule 9 reinforces that tracking must never block the main loop; core + functionality (module mapping, worker dispatch, monitoring) takes priority over status + reporting. + `features/environment.py` now emits its non-assertion exception guard warning to both the structured logger and `stderr` via a new `_warning_with_stderr` helper. This makes the guard firing visible in standard Behave console output and CI log -- 2.52.0