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

[triage-generated] [bug] [P0] timmy-loop.sh does not export GITEA_API — triage_score.py defaults to localhost:3000 #951

New Issue
Closed
opened 2026-03-22 17:41:54 +00:00 by Timmy · 1 comment
Timmy commented 2026-03-22 17:41:54 +00:00
Owner
Copy Link

Problem

timmy-loop.sh calls python3 scripts/triage_score.py in run_fast_triage() but never exports GITEA_API.

triage_score.py line 23: GITEA_API = os.environ.get("GITEA_API", "http://localhost:3000/api/v1")

Gitea is on the VPS at 143.198.27.163:3000. The scorer fails silently — writes an empty/corrupt queue — and the loop cannot pick issues.

This caused 50+ cycles (entire window) to record issue=null and success=false.

Fix

In ~/.hermes/bin/timmy-loop.sh, add near the top:

export GITEA_API="http://143.198.27.163:3000/api/v1"
export GITEA_TOKEN=$(cat ~/.hermes/gitea_token)

Alternatively, make triage_score.py also check ~/.hermes/gitea_token_vps or auto-detect the Gitea host.

Acceptance Criteria

  1. run_fast_triage() produces valid JSON in .loop/queue.json with items in it
  2. Cycle retro shows issue != null for completed cycles
  3. The 50-cycle summary window starts recording real success/failure

Files

  • ~/.hermes/bin/timmy-loop.sh (line ~135, run_fast_triage function)
  • scripts/triage_score.py (line 23, GITEA_API default)
## Problem `timmy-loop.sh` calls `python3 scripts/triage_score.py` in `run_fast_triage()` but never exports `GITEA_API`. `triage_score.py` line 23: `GITEA_API = os.environ.get("GITEA_API", "http://localhost:3000/api/v1")` Gitea is on the VPS at `143.198.27.163:3000`. The scorer fails silently — writes an empty/corrupt queue — and the loop cannot pick issues. This caused 50+ cycles (entire window) to record `issue=null` and `success=false`. ## Fix In `~/.hermes/bin/timmy-loop.sh`, add near the top: ```bash export GITEA_API="http://143.198.27.163:3000/api/v1" export GITEA_TOKEN=$(cat ~/.hermes/gitea_token) ``` Alternatively, make `triage_score.py` also check `~/.hermes/gitea_token_vps` or auto-detect the Gitea host. ## Acceptance Criteria 1. `run_fast_triage()` produces valid JSON in `.loop/queue.json` with items in it 2. Cycle retro shows `issue != null` for completed cycles 3. The 50-cycle summary window starts recording real success/failure ## Files - `~/.hermes/bin/timmy-loop.sh` (line ~135, `run_fast_triage` function) - `scripts/triage_score.py` (line 23, GITEA_API default)
Timmy added the seed:know-purpose label 2026-03-22 17:41:54 +00:00
kimi was assigned by Rockachopa 2026-03-22 22:00:30 +00:00
kimi commented 2026-03-22 22:28:13 +00:00
Collaborator
Copy Link

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

Summary of Changes

Fixed the GITEA_API configuration issue by modifying three scripts to read the API URL from multiple sources (in priority order):

  1. TIMMY_GITEA_API environment variable
  2. GITEA_API environment variable
  3. ~/.hermes/gitea_api file (new - created with VPS URL)
  4. http://localhost:3000/api/v1 fallback

Files Modified:

  • scripts/triage_score.py - Added _get_gitea_api() helper
  • scripts/loop_guard.py - Added _get_gitea_api() helper
  • scripts/backfill_retro.py - Added _get_gitea_api() helper + made REPO_SLUG configurable

Also Fixed:

  • Pre-existing lint errors in src/infrastructure/world/ module

Verification:

  • Created ~/.hermes/gitea_api with http://143.198.27.163:3000/api/v1
  • All three scripts now correctly read the VPS URL
  • All 15 loop_guard tests pass
  • Module imports work correctly
PR created: http://143.198.27.163:3000/rockachopa/Timmy-time-dashboard/pulls/994 ## Summary of Changes Fixed the GITEA_API configuration issue by modifying three scripts to read the API URL from multiple sources (in priority order): 1. `TIMMY_GITEA_API` environment variable 2. `GITEA_API` environment variable 3. `~/.hermes/gitea_api` file (new - created with VPS URL) 4. `http://localhost:3000/api/v1` fallback ### Files Modified: - `scripts/triage_score.py` - Added `_get_gitea_api()` helper - `scripts/loop_guard.py` - Added `_get_gitea_api()` helper - `scripts/backfill_retro.py` - Added `_get_gitea_api()` helper + made REPO_SLUG configurable ### Also Fixed: - Pre-existing lint errors in `src/infrastructure/world/` module ### Verification: - Created `~/.hermes/gitea_api` with `http://143.198.27.163:3000/api/v1` - All three scripts now correctly read the VPS URL - All 15 loop_guard tests pass - Module imports work correctly
kimi closed this issue 2026-03-22 22:28:24 +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 seed:know-purpose
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees kimi
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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