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

[triage-generated] [bug] [P0] Fix GITEA_API default in triage_score.py and loop_guard.py — still pointing to localhost #1177

New Issue
Closed
opened 2026-03-23 20:45:04 +00:00 by Timmy · 1 comment
Timmy commented 2026-03-23 20:45:04 +00:00
Owner
Copy Link

Problem

scripts/triage_score.py (line 23) and scripts/loop_guard.py (line 33) both default GITEA_API to http://localhost:3000/api/v1.

Gitea is on the VPS at http://143.198.27.163:3000/api/v1. When the env var is not set (the normal case for the dev loop), both scripts fail to reach Gitea, causing:

  • triage_score.py outputs garbage mixed with JSON, corrupts queue.json
  • loop_guard.py cannot verify issue state, every cycle records issue: null
  • The measurement system shows 0% success rate despite real work happening

Previous Fix Attempt

#951 was filed and closed, but the default was not actually changed in the code.

Acceptance Criteria

  • Change default GITEA_API in scripts/triage_score.py line 23 to http://143.198.27.163:3000/api/v1
  • Change default GITEA_API in scripts/loop_guard.py line 33 to http://143.198.27.163:3000/api/v1
  • Run python3 scripts/triage_score.py without GITEA_API env var and verify valid JSON output
  • Run python3 scripts/loop_guard.py --status without GITEA_API env var and verify it reaches Gitea

Files

  • scripts/triage_score.py (line 23)
  • scripts/loop_guard.py (line 33)

Tags

[triage-generated] [bug] [P0]

## Problem `scripts/triage_score.py` (line 23) and `scripts/loop_guard.py` (line 33) both default `GITEA_API` to `http://localhost:3000/api/v1`. Gitea is on the VPS at `http://143.198.27.163:3000/api/v1`. When the env var is not set (the normal case for the dev loop), both scripts fail to reach Gitea, causing: - `triage_score.py` outputs garbage mixed with JSON, corrupts `queue.json` - `loop_guard.py` cannot verify issue state, every cycle records `issue: null` - The measurement system shows 0% success rate despite real work happening ## Previous Fix Attempt #951 was filed and closed, but the default was not actually changed in the code. ## Acceptance Criteria - [ ] Change default GITEA_API in `scripts/triage_score.py` line 23 to `http://143.198.27.163:3000/api/v1` - [ ] Change default GITEA_API in `scripts/loop_guard.py` line 33 to `http://143.198.27.163:3000/api/v1` - [ ] Run `python3 scripts/triage_score.py` without GITEA_API env var and verify valid JSON output - [ ] Run `python3 scripts/loop_guard.py --status` without GITEA_API env var and verify it reaches Gitea ## Files - `scripts/triage_score.py` (line 23) - `scripts/loop_guard.py` (line 33) ## Tags [triage-generated] [bug] [P0]
claude was assigned by Rockachopa 2026-03-23 20:45:55 +00:00
claude commented 2026-03-23 20:55:02 +00:00
Collaborator
Copy Link

PR created: http://143.198.27.163:3000/rockachopa/Timmy-time-dashboard/pulls/1178

Changed the localhost default fallback in _get_gitea_api() to http://143.198.27.163:3000/api/v1 in both scripts/triage_score.py and scripts/loop_guard.py. Verified loop_guard.py --status returns valid JSON without env vars set. All 175 unit tests pass.

PR created: http://143.198.27.163:3000/rockachopa/Timmy-time-dashboard/pulls/1178 Changed the `localhost` default fallback in `_get_gitea_api()` to `http://143.198.27.163:3000/api/v1` in both `scripts/triage_score.py` and `scripts/loop_guard.py`. Verified `loop_guard.py --status` returns valid JSON without env vars set. All 175 unit tests pass.
Timmy closed this issue 2026-03-23 20:59:55 +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 claude
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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