Skip to content

ops: pin greenhouse max_concurrent: 1 + document multi-dispatch bug#109

Open
tehreet wants to merge 1 commit into
mainfrom
ops/greenhouse-serialize-and-document-bug
Open

ops: pin greenhouse max_concurrent: 1 + document multi-dispatch bug#109
tehreet wants to merge 1 commit into
mainfrom
ops/greenhouse-serialize-and-document-bug

Conversation

@tehreet
Copy link
Copy Markdown
Owner

@tehreet tehreet commented Apr 28, 2026

Today's dogfood run found a serious orchestration bug in greenhouse — concurrent dispatches share .overstory/session-branch.txt and the canonical repo HEAD, so the LAST dispatched run's merge branch wins and every subsequent ov merge lands work onto the wrong branch. Documents the bug, the recovery (PRs #105-#108 salvaged), and pins the config to max_concurrent: 1 to prevent recurrence.

🤖 Generated with Claude Code

Today's dogfood run dispatched 5 issues concurrently. The greenhouse
dispatcher writes .overstory/session-branch.txt and checks out the
per-run merge branch on EVERY dispatch — with concurrent dispatches
the LAST checkout wins, and every subsequent ov merge lands the wrong
builder's work onto the wrong run's merge branch.

Net result: greenhouse/promptionary-d414 (issue #93's branch) ended
up with merges from #91 + #89's builders. Issue #92's builder branch
was contaminated similarly.

Salvaged 4 clean focused commits from the overstory/builder-* branches
into PRs #105 (#90), #106 (#89), #107 (#91), #108 (#92).

Mitigation:
- Drop max_concurrent from 5 → 1 so dispatches serialize. The proper
  fix in greenhouse is to use git worktree per merge branch instead
  of swapping HEAD on the canonical repo.
- Document the bug + recovery in docs/agent-factory-status.md.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 28, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
promptionary Ready Ready Preview, Comment Apr 28, 2026 5:03am

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant