Timmy_Foundation/timmy-config
15
0
Fork 0
Code Issues 99 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

[BUG] Velocity engine self-generation fails with HTTP 422 and KeyError total_claimed #239

New Issue
Open
opened 2026-04-06 13:26:01 +00:00 by Timmy · 0 comments
Timmy commented 2026-04-06 13:26:01 +00:00
Owner
Copy Link

The nightly landscape showed the velocity engine falseworking instead of feeding the queue.

Observed last night:

  • 0 issues claimed
  • 0 issues created
  • repeated self-generation failures with HTTP 422
  • terminal/log evidence of a crash at the end with KeyError: 'total_claimed'

Why this matters:

  • Broken backlog generation makes the fleet look alive while producing no valid new work.
  • Overnight automations should be paused when structurally broken, but the durable fix is to repair the engine.

Acceptance criteria:

  • python3 ~/.hermes/velocity-engine.py completes without KeyError: 'total_claimed'.
  • The script reports correct counters for scanned, claimed, and created issues.
  • Self-generation requests use valid payloads for this forge (no blanket HTTP 422 across repos).
  • A dry run against current repos produces a truthful summary even when zero issues are created.
  • The cron can be safely resumed after one successful manual proof run.

Implementation hint:

  • Check issue-create payload shape against the current forge rules (labels/assignees/milestones/body fields), not old assumptions.
The nightly landscape showed the velocity engine falseworking instead of feeding the queue. Observed last night: - `0` issues claimed - `0` issues created - repeated self-generation failures with `HTTP 422` - terminal/log evidence of a crash at the end with `KeyError: 'total_claimed'` Why this matters: - Broken backlog generation makes the fleet look alive while producing no valid new work. - Overnight automations should be paused when structurally broken, but the durable fix is to repair the engine. Acceptance criteria: - [ ] `python3 ~/.hermes/velocity-engine.py` completes without `KeyError: 'total_claimed'`. - [ ] The script reports correct counters for scanned, claimed, and created issues. - [ ] Self-generation requests use valid payloads for this forge (no blanket `HTTP 422` across repos). - [ ] A dry run against current repos produces a truthful summary even when zero issues are created. - [ ] The cron can be safely resumed after one successful manual proof run. Implementation hint: - Check issue-create payload shape against the current forge rules (labels/assignees/milestones/body fields), not old assumptions.
Timmy self-assigned this 2026-04-06 13:26:01 +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
 assigned-sonnet
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
 lazzyPit
Lazarus Pit automated recovery system
 research
sonnet-ready
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 hermes kimi manus perplexity sonnet
No Assignees Timmy
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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