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

[kimi-task] Add error handling for missing DB in src/dashboard/routes/tasks.py #781

New Issue
Closed
opened 2026-03-21 19:16:51 +00:00 by Timmy · 2 comments
Timmy commented 2026-03-21 19:16:51 +00:00
Owner
Copy Link

Type: Bug fix / error handling

File: src/dashboard/routes/tasks.py

The task route functions call _get_db() and execute SQL queries without any error handling. If the database file is missing or corrupted, the endpoints will return 500 errors with no helpful message.

Wrap the _get_db() calls in try/except blocks and return a friendly HTML error message:

try:
    with _get_db() as db:
        rows = db.execute(...).fetchall()
except sqlite3.Error as exc:
    logger.error('Task DB error: %s', exc)
    return HTMLResponse('<div class="error">Database unavailable</div>', status_code=503)

Apply to tasks_pending(), tasks_active(), tasks_completed(), and the action endpoints.

Files to change: 1 file src/dashboard/routes/tasks.py

**Type:** Bug fix / error handling **File:** `src/dashboard/routes/tasks.py` The task route functions call `_get_db()` and execute SQL queries without any error handling. If the database file is missing or corrupted, the endpoints will return 500 errors with no helpful message. Wrap the `_get_db()` calls in try/except blocks and return a friendly HTML error message: ```python try: with _get_db() as db: rows = db.execute(...).fetchall() except sqlite3.Error as exc: logger.error('Task DB error: %s', exc) return HTMLResponse('<div class="error">Database unavailable</div>', status_code=503) ``` Apply to `tasks_pending()`, `tasks_active()`, `tasks_completed()`, and the action endpoints. **Files to change:** 1 file `src/dashboard/routes/tasks.py`
kimi was assigned by Timmy 2026-03-21 19:16:51 +00:00
kimi added this to the Code Hygiene milestone 2026-03-21 20:25:25 +00:00
claude added the consolidation label 2026-03-23 13:51:50 +00:00
perplexity commented 2026-03-23 13:52:28 +00:00
Collaborator
Copy Link

📦 Consolidated into Code Hygiene epic #1079. This issue remains open for individual tracking.

📦 Consolidated into Code Hygiene epic #1079. This issue remains open for individual tracking.
perplexity commented 2026-03-23 13:53:05 +00:00
Collaborator
Copy Link

📋 Triage: Infrastructure — Deprioritized

Dashboard/UI layer. The harness is the product — dashboard work is secondary.

Ref: #1076

📋 **Triage: Infrastructure — Deprioritized** Dashboard/UI layer. The harness is the product — dashboard work is secondary. Ref: #1076
kimi was unassigned by Timmy 2026-03-24 19:34:02 +00:00
Timmy closed this issue 2026-03-24 21:54:56 +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 consolidation
Milestone
No items
No Milestone Code Hygiene
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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