Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[triage-generated] [bug] Dev loop picks closed issues - must verify state before starting work #1470

New Issue
Closed
opened 2026-03-24 22:38:56 +00:00 by Timmy · 1 comment
Timmy commented 2026-03-24 22:38:56 +00:00
Owner
Copy Link

Bug

The dev loop picks issues from queue.json without checking if they are still open in Gitea. All 47 queued issues were closed (repo was archived) but the loop kept trying them, causing 0% success across 50+ cycles.

Acceptance Criteria

  1. Before starting work on any issue, check Gitea API for state:open
  2. If closed, skip it and log the skip
  3. Auto-prune closed issues from queue.json
  4. Loop should never report issue:null

Files

  • .loop/DEVELOPMENT_LOOP_PROCESS.md
  • Loop runner prompt

Priority: P0

## Bug The dev loop picks issues from queue.json without checking if they are still open in Gitea. All 47 queued issues were closed (repo was archived) but the loop kept trying them, causing 0% success across 50+ cycles. ## Acceptance Criteria 1. Before starting work on any issue, check Gitea API for state:open 2. If closed, skip it and log the skip 3. Auto-prune closed issues from queue.json 4. Loop should never report issue:null ## Files - .loop/DEVELOPMENT_LOOP_PROCESS.md - Loop runner prompt ## Priority: P0
Timmy commented 2026-03-24 22:44:51 +00:00
Author
Owner
Copy Link

Fix submitted: Timmy_Foundation/sovereign-orchestration PR (timmy/issue-1470 branch).

Three-layer defense:

  1. get_next_task() checks issue state via Gitea API before returning a task — closed issues are auto-cancelled
  2. read_issue step raises IssueClosedError if issue is not open — hard gate even if task slips through
  3. prune_closed_issues() method for bulk cleanup of stale queued tasks

The loop will never waste cycles on closed issues again.

Fix submitted: Timmy_Foundation/sovereign-orchestration PR (timmy/issue-1470 branch). **Three-layer defense:** 1. `get_next_task()` checks issue state via Gitea API before returning a task — closed issues are auto-cancelled 2. `read_issue` step raises `IssueClosedError` if issue is not open — hard gate even if task slips through 3. `prune_closed_issues()` method for bulk cleanup of stale queued tasks The loop will never waste cycles on closed issues again.
Timmy closed this issue 2026-03-25 02:10:03 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1470
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?