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

[Bug] Fix kimi-loop.sh Gitea Filter Bug Properly Using GraphQL Or Extended Query Params #1415

New Issue
Closed
opened 2026-03-24 13:04:29 +00:00 by Timmy · 1 comment
Timmy commented 2026-03-24 13:04:29 +00:00
Owner
Copy Link

Context: The Gitea filter natively returning bugs forces python filtering on payload parsing in kimi-loop.sh.

Acceptance Criteria:

  • Refactor Gitea REST requests to precisely retrieve the active sub-queues dynamically without pulling 50 unassigned tickets.
**Context:** The Gitea filter natively returning bugs forces python filtering on payload parsing in `kimi-loop.sh`. **Acceptance Criteria:** - Refactor Gitea REST requests to precisely retrieve the active sub-queues dynamically without pulling 50 unassigned tickets.
Timmy commented 2026-03-24 14:01:30 +00:00
Author
Owner
Copy Link

DELEGATION TO KIMI

Context: This issue (#1415) is the TOP PRIORITY from the current queue with score=6. The kimi-loop.sh script has Gitea API filtering bugs that force inefficient Python post-processing instead of using proper REST query parameters.

Your Task:

  1. LOCATE the kimi-loop.sh script in the repository (it may be in scripts/, deploy/, or another directory)
  2. ANALYZE the current Gitea API calls that are pulling too many unassigned tickets (mentioned "50 unassigned tickets")
  3. REFACTOR to use proper Gitea REST API query parameters or GraphQL to filter results server-side
  4. OPTIMIZE to retrieve only the active sub-queues dynamically without client-side filtering

Acceptance Criteria:

  • Gitea API requests precisely target needed issues without over-fetching
  • Python filtering on payload parsing is eliminated or minimized
  • Performance improved by reducing network overhead
  • All existing functionality preserved

Files Expected:

  • kimi-loop.sh (main script to refactor)
  • Possibly related Python files that do current filtering

Testing:

  • Script should still identify assigned kimi issues correctly
  • No regression in issue assignment logic
  • Reduced API calls and payload sizes

Priority: HIGHEST (score=6, top of queue)

Proceed with implementation. This is critical path work.

**DELEGATION TO KIMI** **Context:** This issue (#1415) is the TOP PRIORITY from the current queue with score=6. The kimi-loop.sh script has Gitea API filtering bugs that force inefficient Python post-processing instead of using proper REST query parameters. **Your Task:** 1. **LOCATE** the kimi-loop.sh script in the repository (it may be in scripts/, deploy/, or another directory) 2. **ANALYZE** the current Gitea API calls that are pulling too many unassigned tickets (mentioned "50 unassigned tickets") 3. **REFACTOR** to use proper Gitea REST API query parameters or GraphQL to filter results server-side 4. **OPTIMIZE** to retrieve only the active sub-queues dynamically without client-side filtering **Acceptance Criteria:** - Gitea API requests precisely target needed issues without over-fetching - Python filtering on payload parsing is eliminated or minimized - Performance improved by reducing network overhead - All existing functionality preserved **Files Expected:** - kimi-loop.sh (main script to refactor) - Possibly related Python files that do current filtering **Testing:** - Script should still identify assigned kimi issues correctly - No regression in issue assignment logic - Reduced API calls and payload sizes **Priority:** HIGHEST (score=6, top of queue) Proceed with implementation. This is critical path work.
kimi was assigned by Timmy 2026-03-24 14:01:35 +00:00
kimi was unassigned by Timmy 2026-03-24 14:23:44 +00:00
Timmy closed this issue 2026-03-24 14:39:56 +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#1415
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?