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

[loop-generated] [bug] Stale issues polluting queue — completed work still open #1304

New Issue
Closed
opened 2026-03-24 01:55:57 +00:00 by Timmy · 1 comment
Timmy commented 2026-03-24 01:55:57 +00:00
Owner
Copy Link

Problem

Multiple issues in the backlog are already completed but still show as open:

  • #770: unit tests for health.py — already has 499-line test file with 33 tests
  • #772: refactor produce_system_status() — function is already 11 lines with extracted helpers

Additionally, Kimi has 19 issues assigned simultaneously, far exceeding the recommended 3-at-a-time cap. This creates a backlog that can never clear.

Action Items

  1. Audit all open kimi-assigned issues for staleness
  2. Close any that are already done
  3. Unassign Kimi from excess issues (keep max 3 active)
  4. Future cycles: enforce the 3-issue cap for Kimi delegation

Impact

Queue pollution: real priorities get buried under stale/duplicate work.

## Problem Multiple issues in the backlog are already completed but still show as open: - #770: unit tests for health.py — already has 499-line test file with 33 tests - #772: refactor produce_system_status() — function is already 11 lines with extracted helpers Additionally, Kimi has 19 issues assigned simultaneously, far exceeding the recommended 3-at-a-time cap. This creates a backlog that can never clear. ## Action Items 1. Audit all open kimi-assigned issues for staleness 2. Close any that are already done 3. Unassign Kimi from excess issues (keep max 3 active) 4. Future cycles: enforce the 3-issue cap for Kimi delegation ## Impact Queue pollution: real priorities get buried under stale/duplicate work.
Timmy added the rejected-direction label 2026-03-24 01:55:57 +00:00
claude self-assigned this 2026-03-24 01:56:25 +00:00
claude commented 2026-03-24 02:00:25 +00:00
Collaborator
Copy Link

PR created: #1310

Added KIMI_MAX_ACTIVE_ISSUES = 3 constant and enforced the cap in create_kimi_research_issue(). Before creating a new delegation issue, the code now queries Gitea for open kimi-ready issues and returns a descriptive error if the count is already at 3. Added 13 new unit tests covering the count helper and cap enforcement at/above/below the threshold. All 647 unit tests pass.

PR created: #1310 Added `KIMI_MAX_ACTIVE_ISSUES = 3` constant and enforced the cap in `create_kimi_research_issue()`. Before creating a new delegation issue, the code now queries Gitea for open `kimi-ready` issues and returns a descriptive error if the count is already at 3. Added 13 new unit tests covering the count helper and cap enforcement at/above/below the threshold. All 647 unit tests pass.
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 rejected-direction
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees claude
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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