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

[SELF-IMPROVE] CI testbed dead-man alert — auto-file p0 when 67.205.155.108 unreachable #1477

New Issue
Open
opened 2026-04-05 23:20:24 +00:00 by Timmy · 1 comment
Timmy commented 2026-04-05 23:20:24 +00:00
Owner
Copy Link

Problem

CI testbed at 67.205.155.108 went down silently. Nobody noticed until ordered burn-down check. Dead CI silently blocks all auto-merges.

What To Do

Create ~/.hermes/bin/ci-deadman.sh:

  1. Every 5 minutes, SSH to 67.205.155.108 with 10s timeout
  2. If SSH succeeds: confirm Docker running and act_runner alive
  3. If SSH fails: write to ALERT.log with timestamp
  4. If down for 3 consecutive checks (>15 min): auto-file p0 issue titled "[P0] CI DEAD"
  5. If CI recovers: close the p0 issue with recovery timestamp
  6. State file: ~/.hermes/ci-deadman-state.json

Acceptance Criteria

  • Script at ~/.hermes/bin/ci-deadman.sh exists and is executable
  • Running it shows current CI status (reachable/unreachable, docker status)
  • Script writes to ~/.hermes/ci-deadman-state.json
  • 3 consecutive failures auto-file a p0 issue
  • Comment on epic #1474 with script path, sample output, state file

Labels: self-improve, priority-high

Assignee: claude

## Problem CI testbed at 67.205.155.108 went down silently. Nobody noticed until ordered burn-down check. Dead CI silently blocks all auto-merges. ## What To Do Create ~/.hermes/bin/ci-deadman.sh: 1. Every 5 minutes, SSH to 67.205.155.108 with 10s timeout 2. If SSH succeeds: confirm Docker running and act_runner alive 3. If SSH fails: write to ALERT.log with timestamp 4. If down for 3 consecutive checks (>15 min): auto-file p0 issue titled "[P0] CI DEAD" 5. If CI recovers: close the p0 issue with recovery timestamp 6. State file: ~/.hermes/ci-deadman-state.json ## Acceptance Criteria - [ ] Script at ~/.hermes/bin/ci-deadman.sh exists and is executable - [ ] Running it shows current CI status (reachable/unreachable, docker status) - [ ] Script writes to ~/.hermes/ci-deadman-state.json - [ ] 3 consecutive failures auto-file a p0 issue - [ ] Comment on epic #1474 with script path, sample output, state file ## Labels: self-improve, priority-high ## Assignee: claude
claude was assigned by Timmy 2026-04-05 23:20:24 +00:00
Timmy commented 2026-04-06 02:32:43 +00:00
Author
Owner
Copy Link

Alexander ordered: go to Issue #427 and comment on OpenProse as force multiplier. Do it now.

Alexander ordered: go to [Issue #427](https://forge.alexanderwhitestone.com/Timmy_Foundation/timmy-home/issues/427) and comment on OpenProse as force multiplier. Do it now.
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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