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

Implement Graceful Degradation Test Scenarios #919

New Issue
Closed
opened 2026-03-22 14:15:41 +00:00 by antigravity · 1 comment
antigravity commented 2026-03-22 14:15:41 +00:00
Collaborator
Copy Link

The system mandates graceful degradation when Ollama, Redis, or AirLLM go down, but these paths are severely under-tested. Create test cases specifically for simulating service failures and assessing the fallback logic.

The system mandates graceful degradation when Ollama, Redis, or AirLLM go down, but these paths are severely under-tested. Create test cases specifically for simulating service failures and assessing the fallback logic.
claude was assigned by Rockachopa 2026-03-22 23:31:45 +00:00
claude commented 2026-03-24 01:49:48 +00:00
Collaborator
Copy Link

PR created: http://143.198.27.163:3000/Rockachopa/Timmy-time-dashboard/pulls/1291

Added tests/infrastructure/test_graceful_degradation.py with 35 test cases covering all the under-tested fallback paths:

  • Ollama health-check failures (connection refused, timeout, HTTP 503/500, generic exception) → provider excluded from cascade
  • requests library absent → Ollama and vllm-mlx optimistically assume availability
  • Cascade failover: Ollama connection error → Anthropic cloud fallback used
  • Circuit-breaker full lifecycle: CLOSED → OPEN (N failures) → HALF_OPEN (timeout elapsed) → CLOSED (test successes), plus HALF_OPEN failure re-opens
  • All providers fail → RuntimeError lists individual errors
  • ClaudeBackend/GrokBackend graceful degradation: no-key and API-error paths
  • Chat store SQLite resilience: directory auto-creation, concurrent writes (thread-safe), ordering, recent(), pruning

All 505 unit tests pass.

PR created: http://143.198.27.163:3000/Rockachopa/Timmy-time-dashboard/pulls/1291 Added `tests/infrastructure/test_graceful_degradation.py` with 35 test cases covering all the under-tested fallback paths: - **Ollama health-check failures** (connection refused, timeout, HTTP 503/500, generic exception) → provider excluded from cascade - **`requests` library absent** → Ollama and vllm-mlx optimistically assume availability - **Cascade failover**: Ollama connection error → Anthropic cloud fallback used - **Circuit-breaker full lifecycle**: CLOSED → OPEN (N failures) → HALF_OPEN (timeout elapsed) → CLOSED (test successes), plus HALF_OPEN failure re-opens - **All providers fail** → RuntimeError lists individual errors - **ClaudeBackend/GrokBackend** graceful degradation: no-key and API-error paths - **Chat store SQLite resilience**: directory auto-creation, concurrent writes (thread-safe), ordering, recent(), pruning All 505 unit tests pass.
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#919
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?