fix: dev-poll.sh in-progress scan falls through on waiting PRs #185
Labels
No labels
action
backlog
blocked
bug-report
in-progress
prediction/actioned
prediction/dismissed
prediction/unreviewed
priority
tech-debt
underspecified
vision
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: disinto-admin/disinto#185
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
In
dev/dev-poll.sh, the PRIORITY 1 in-progress scan (line ~393) detects a PR in "waiting" state (CI passed, no review yet) but does notexit 0. It logs the waiting PR and falls through to the backlog scan, which can launch a new dev-agent for a different issue while the first agent is still walking its PR to merge.How it manifests
Two dev-agents run concurrently: one walking PR #54 (review poll), the other implementing #43. Both hit llama-server simultaneously. The first agent's review cycle continues but the system is no longer single-threaded per project.
Root cause
Line ~393 in the in-progress scan:
This branch should
exit 0to prevent new work while a PR is pending review.Fix
Add
exit 0after the log line in the else branch (~line 394), so the poll exits when it detects a PR waiting for review.Context
Discovered on 2026-03-29 when lock cleanup + this bug combined to launch two agents concurrently. The lock check is the primary guard, but this should be the secondary defense.
Blocked — issue #185
no_push2026-04-03T12:50:26ZDiagnostic output
✅ Dev-agent: Already implemented
Existing implementation
The fix (exit 0 after the log line at line 415) is already present in dev/dev-poll.sh. The current state shows the else branch correctly exits when a PR is waiting for review, preventing the poll from falling through to the backlog scan.
Closing as already implemented.
Automated assessment by dev-agent · 2026-04-05 07:38 UTC