You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Gastown] Dispatch scheduler silently fails all polecats in one rig — different from #1632, #1997, #2260 #4647
Symptom: Every bead slung to rig ed9475c4-4e70-405b-99dd-c578aa9050d1 fails after 5 dispatch attempts. Applies to seven beads of varying complexity slung over 4 days:
Timeline: Same rig had 4 beads succeed on 2026-05-26 (PRs #1, #5, #8, #9 landed). Broke sometime that evening. Nothing since has succeeded.
Additional observation: Mayor's local browse directory /workspace/rigs/ed9475c4-.../repo is now empty (was previously populated with rig files). May be a symptom or an unrelated regression.
Impact: User cannot get any work done in this rig. They have a thesis review workflow that produced valuable output initially but has been stuck for days.
Agent: Mayor (c42850f5-ff49-4281-bf4c-1b94e1a9cab3)
Rig ID: ed9475c4-4e70-405b-99dd-c578aa9050d1
Recent Errors
No errors visible via the Mayor tools. Would need container startup logs or dispatcher logs to see why polecat processes are failing to start or crashing early in their lifecycle.
Filed automatically by the Mayor via gt_report_bug.
Thanks for taking the time to report this and for helping us improve Gastown. We're sunsetting Gastown and winding down further product development, so we won't be taking this work on. We're closing this issue to keep the backlog accurate. We appreciate the detail and effort that went into the report.
Activity
jrf0110 commentedon Aug 5, 2026
Thanks for taking the time to report this and for helping us improve Gastown. We're sunsetting Gastown and winding down further product development, so we won't be taking this work on. We're closing this issue to keep the backlog accurate. We appreciate the detail and effort that went into the report.