fix(vision-manager): LOW watermark must not idle-stop a running vision #9

fabi · 2026-06-16T16:57:45Z

fabi commented

2026-06-16 16:57:45 +00:00

Back-ports the host hotfix. LOW (start-inhibit) watermark forced pending=0 → idle path killed a working vision at ~80% instead of the 92% HIGH stop. Split levers via mem_block_start (blocks START only). Verified live on the host.

fabi added 1 commit 2026-06-16 16:57:46 +00:00

fix(vision-manager): LOW watermark must not idle-stop a running vision

deploy / test-frontend (pull_request) Waiting to run

Details

deploy / build-and-push (pull_request) Blocked by required conditions

Details

deploy / deploy (pull_request) Blocked by required conditions

Details

deploy / test-backend (pull_request) Has been cancelled

Details

934f39abe6

The memory-yield LOW (start-inhibit) watermark forced pending=0, which the
idle-debounce path then read as 'no work' and used to idle-stop a RUNNING,
actively-analyzing vision once the box floated past LOW (idle stack + LLM
≈ 80% on this Pi) — so vision was killed mid-analysis at ~80%, not the 92%
HIGH watermark. Split the two levers: LOW now sets a mem_block_start flag
that only holds off STARTING a stopped vision; only the HIGH active stop (or
a genuinely drained queue) stops a running one. Observed live: vision now
holds through the 79–81% band and completes pages.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

fabi merged commit 32fcebd47a into main

2026-06-16 16:57:50 +00:00

fabi referenced this issue from a commit

2026-06-16 16:57:50 +00:00

fix(vision-manager): LOW watermark must not idle-stop a running vision (#9)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: fabi/Mangalord#9