Re-file the issues no bee can take again - #4441
Merged
Merged
Conversation
A dispatch row that spends its retry ceiling is released once, after an hour, and then stays rejected on purpose - "a third identical failure is evidence about the issue, not about the attempt". The rule is right; its consequence was never acted on. The ISSUE stays claimed, so no bee can take it again however much the brief improves. Measured: 101 open issues carried a queen-* branch, no pull request and no running bee. 92 sat behind a branch that was empty or had NO MERGE BASE with master - orphan debris from before the container stopped cloning shallow - held since 2026-09-17, through two corrections to the brief they were written against (#4296, #4302). There is no external way to release a row, so this copies the work into a new issue, which has no row, and closes the old with a pointer. Title, body and `## Boundary` carry over byte for byte; the new issue also carries today's toolbelt. Measured after running it over all 92: the review column fell from 59 to 15, the backlog rose from 553 to 590, and the swarm's next dispatch was #4429 - one of the re-filed issues. The tool found its own blind spot first: `git diff A...B` on histories with no merge base prints `fatal: ... no merge base` to STDERR and exits non-zero, and the helper returned stdout and stderr together - so that sentence read as "this branch changed one file" and 93 branches were skipped as work to publish. CENSUS: quiet 59 -> 60 workflow files; shell 59 -> 60 files, 80 -> 81 jobs, 272 -> 273 run-steps, 251 -> 252 run with `bash -eo pipefail`. Classified in check_pr_branch_filters.py in the same commit. Closes #4440 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Sep 20, 2026
Merged
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #4440
A dispatch row that spends its retry ceiling is released once, then stays
rejectedon purpose — "a third identical failure is evidence about the issue,not about the attempt". Right rule. Its consequence was never acted on: the
issue stays claimed, so no bee can take it again however much the brief
improves.
Measured after running it over all 92
reviewbacklogIt found its own blind spot first
git diff A...Bon histories with no merge base printsfatal: ... no merge baseto stderr and exits non-zero. The helper returned stdout and stderrtogether, so that sentence read as "this branch changed one file" — and 93
branches were skipped as work to publish. Same defect class as a feeder that
exits green when it cannot see the swarm.
What it refuses
A branch with real commits (that is work to publish), a branch newer than
the cutoff, an issue that already has a pull request, an issue a bee is running
right now — and everything, if the board does not answer.
Daily at 04:41 with a two-day cutoff, so nothing in flight is ever touched.
Both ledgers a new workflow moves are updated in this same commit.
🤖 Generated with Claude Code