Timmy_Foundation/timmy-config
16
0
Fork 0
Code Issues 57 Pull Requests 1 Actions 1 Packages Projects Releases Wiki Activity

Verify Huey tasks — 24-hour health check on all 10 periodic tasks #4

New Issue
Closed
opened 2026-03-25 23:27:30 +00:00 by Timmy · 6 comments
Timmy commented 2026-03-25 23:27:30 +00:00
Owner
Copy Link

Context

All 10 Huey tasks were deployed on 2026-03-25. Each was manually triggered and confirmed working. This issue is the follow-up: come back after 24 hours and verify they're running correctly on schedule.

Tasks to verify

Original 3 (from Perplexity)

  • triage_issues (every 15m) — check Huey log for executions, verify no 404 errors
  • review_prs (every 30m) — check if PR size comments are appearing correctly on repos
  • dispatch_assigned (every 10m) — check for dispatch comments, verify no double-dispatching

New 6 (from this session)

  • sync_config_up (hourly) — verify git log in timmy-config shows hourly sync commits
  • session_export (every 4h) — check ~/.timmy/training-data/dpo-pairs/ has new files, verify JSON structure is valid DPO format
  • model_health (every 5m) — check ~/.hermes/model_health.json has recent timestamp, verify Ollama recovery after restart
  • heartbeat_tick (every 10m) — check ~/.timmy/heartbeat/ticks_YYYYMMDD.jsonl has entries every 10 minutes, verify perception data is meaningful
  • memory_compress (daily 8AM) — check ~/.timmy/briefings/ for a briefing file after 8AM runs
  • repo_watchdog (every 20m) — check ~/.hermes/watchdog_state.json shows updated issue/PR numbers

How to verify

# Check Huey is still running
ps aux | grep huey | grep -v grep

# Check for errors in last 24h
grep ERROR ~/.hermes/logs/huey.log | tail -20

# Check execution counts
grep 'executed' ~/.hermes/logs/huey.log | wc -l

# Check heartbeat ticks
wc -l ~/.timmy/heartbeat/ticks_$(date +%Y%m%d).jsonl

# Check training data
ls ~/.timmy/training-data/dpo-pairs/ | wc -l

# Check model health freshness
cat ~/.hermes/model_health.json | python3 -c "import sys,json; print(json.load(sys.stdin)['timestamp'])"

Known issues from deployment

  • autolora repo was 404'ing (removed from REPOS list — it's local only)
  • dispatch_assigned and triage_issues were failing due to autolora 404 (fixed)
  • memory_compress hasn't fired yet (waits for 8AM)

If Huey died

cd ~/.timmy/timmy-config && nohup huey_consumer.py tasks.huey -w 2 -k thread -v >> ~/.hermes/logs/huey.log 2>&1 &
## Context All 10 Huey tasks were deployed on 2026-03-25. Each was manually triggered and confirmed working. This issue is the follow-up: come back after 24 hours and verify they're running correctly on schedule. ## Tasks to verify ### Original 3 (from Perplexity) - [ ] `triage_issues` (every 15m) — check Huey log for executions, verify no 404 errors - [ ] `review_prs` (every 30m) — check if PR size comments are appearing correctly on repos - [ ] `dispatch_assigned` (every 10m) — check for dispatch comments, verify no double-dispatching ### New 6 (from this session) - [ ] `sync_config_up` (hourly) — verify `git log` in timmy-config shows hourly sync commits - [ ] `session_export` (every 4h) — check `~/.timmy/training-data/dpo-pairs/` has new files, verify JSON structure is valid DPO format - [ ] `model_health` (every 5m) — check `~/.hermes/model_health.json` has recent timestamp, verify Ollama recovery after restart - [ ] `heartbeat_tick` (every 10m) — check `~/.timmy/heartbeat/ticks_YYYYMMDD.jsonl` has entries every 10 minutes, verify perception data is meaningful - [ ] `memory_compress` (daily 8AM) — check `~/.timmy/briefings/` for a briefing file after 8AM runs - [ ] `repo_watchdog` (every 20m) — check `~/.hermes/watchdog_state.json` shows updated issue/PR numbers ## How to verify ```bash # Check Huey is still running ps aux | grep huey | grep -v grep # Check for errors in last 24h grep ERROR ~/.hermes/logs/huey.log | tail -20 # Check execution counts grep 'executed' ~/.hermes/logs/huey.log | wc -l # Check heartbeat ticks wc -l ~/.timmy/heartbeat/ticks_$(date +%Y%m%d).jsonl # Check training data ls ~/.timmy/training-data/dpo-pairs/ | wc -l # Check model health freshness cat ~/.hermes/model_health.json | python3 -c "import sys,json; print(json.load(sys.stdin)['timestamp'])" ``` ## Known issues from deployment - `autolora` repo was 404'ing (removed from REPOS list — it's local only) - `dispatch_assigned` and `triage_issues` were failing due to autolora 404 (fixed) - `memory_compress` hasn't fired yet (waits for 8AM) ## If Huey died ```bash cd ~/.timmy/timmy-config && nohup huey_consumer.py tasks.huey -w 2 -k thread -v >> ~/.hermes/logs/huey.log 2>&1 & ```
Timmy self-assigned this 2026-03-25 23:27:31 +00:00
Timmy commented 2026-03-26 12:31:02 +00:00
Author
Owner
Copy Link

⚡ Dispatched to claude. Huey task queued.

⚡ Dispatched to `claude`. Huey task queued.
Timmy commented 2026-03-26 12:31:04 +00:00
Author
Owner
Copy Link

⚡ Dispatched to gemini. Huey task queued.

⚡ Dispatched to `gemini`. Huey task queued.
Timmy commented 2026-03-26 12:31:06 +00:00
Author
Owner
Copy Link

⚡ Dispatched to kimi. Huey task queued.

⚡ Dispatched to `kimi`. Huey task queued.
Timmy commented 2026-03-26 12:31:07 +00:00
Author
Owner
Copy Link

⚡ Dispatched to grok. Huey task queued.

⚡ Dispatched to `grok`. Huey task queued.
Timmy commented 2026-03-26 12:31:08 +00:00
Author
Owner
Copy Link

⚡ Dispatched to perplexity. Huey task queued.

⚡ Dispatched to `perplexity`. Huey task queued.
Timmy commented 2026-03-28 04:53:14 +00:00
Author
Owner
Copy Link

Closing during the 2026-03-28 backlog burn-down.

Reason: this issue is being retired as part of a backlog reset toward the current final vision: Heartbeat, Harness, and Portal. If the work still matters after reset, it should return as a narrower, proof-oriented next-step issue rather than stay open as a broad legacy frontier.

Closing during the 2026-03-28 backlog burn-down. Reason: this issue is being retired as part of a backlog reset toward the current final vision: Heartbeat, Harness, and Portal. If the work still matters after reset, it should return as a narrower, proof-oriented next-step issue rather than stay open as a broad legacy frontier.
Timmy closed this issue 2026-03-28 04:53:15 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 enhancement
epic
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 research
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity
No Assignees Timmy
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#4
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?