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

[loop-generated] [bug] Pre-existing test failures block all commits via git hooks #1112

New Issue
Closed
opened 2026-03-23 18:07:24 +00:00 by Timmy · 1 comment
Timmy commented 2026-03-23 18:07:24 +00:00
Owner
Copy Link

What's happening

10 tests on main are failing, all with the same root cause:

TypeError: cannot use 'tuple' as a dict key (unhashable type: 'dict')

Affected tests:

  • tests/dashboard/test_calm.py (6 tests) — all calm task endpoints return 500
  • tests/dashboard/test_round4_fixes.py (2 tests) — /tools page returns 500
  • tests/test_smoke.py (2 tests) — /tools endpoint 500

Because the pre-commit hook runs tox -e unit and the pre-push hook runs tox -e pre-push, no commits or pushes can succeed on any branch. This blocks all development.

Root cause

Somewhere in the calm task routes or tools page, a tuple is being used as a dict key where a hashable type is expected. The error cannot use 'tuple' as a dict key (unhashable type: 'dict') suggests a dict is being used where a hashable value is needed.

Expected behavior

All tests on main should pass. Git hooks should not block unrelated work.

Suggested fix

  1. Fix the unhashable type error in the calm/tools routes
  2. OR: temporarily mark these 10 tests as xfail so hooks don't block all development

Acceptance criteria

  • tox -e unit passes on main with 0 failures
  • Git hooks (pre-commit, pre-push) complete successfully
## What's happening 10 tests on main are failing, all with the same root cause: ``` TypeError: cannot use 'tuple' as a dict key (unhashable type: 'dict') ``` Affected tests: - `tests/dashboard/test_calm.py` (6 tests) — all calm task endpoints return 500 - `tests/dashboard/test_round4_fixes.py` (2 tests) — /tools page returns 500 - `tests/test_smoke.py` (2 tests) — /tools endpoint 500 Because the pre-commit hook runs `tox -e unit` and the pre-push hook runs `tox -e pre-push`, **no commits or pushes can succeed** on any branch. This blocks all development. ## Root cause Somewhere in the calm task routes or tools page, a tuple is being used as a dict key where a hashable type is expected. The error `cannot use 'tuple' as a dict key (unhashable type: 'dict')` suggests a dict is being used where a hashable value is needed. ## Expected behavior All tests on main should pass. Git hooks should not block unrelated work. ## Suggested fix 1. Fix the unhashable type error in the calm/tools routes 2. OR: temporarily mark these 10 tests as `xfail` so hooks don't block all development ## Acceptance criteria - `tox -e unit` passes on main with 0 failures - Git hooks (pre-commit, pre-push) complete successfully
Timmy added the seed:serve-real label 2026-03-23 18:07:24 +00:00
claude self-assigned this 2026-03-23 18:07:56 +00:00
claude commented 2026-03-23 18:14:29 +00:00
Collaborator
Copy Link

PR created: http://143.198.27.163:3000/rockachopa/Timmy-time-dashboard/pulls/1115

Root cause: Starlette 1.0.0 changed TemplateResponse signature from (name, context) to (request, name, context). Old-style calls passed the context dict as name, causing Jinja2 to wrap it in a tuple for its cache key, raising TypeError: cannot use 'tuple' as a dict key (unhashable type: 'dict') in Python 3.14.

Fix: Updated 7 TemplateResponse calls across calm.py (6 endpoints) and tools.py (1 endpoint) to use the new Starlette 1.0.0 API.

Result: tox -e unit passes with 3242 passed, 0 failed.

PR created: http://143.198.27.163:3000/rockachopa/Timmy-time-dashboard/pulls/1115 **Root cause:** Starlette 1.0.0 changed `TemplateResponse` signature from `(name, context)` to `(request, name, context)`. Old-style calls passed the context dict as `name`, causing Jinja2 to wrap it in a tuple for its cache key, raising `TypeError: cannot use 'tuple' as a dict key (unhashable type: 'dict')` in Python 3.14. **Fix:** Updated 7 `TemplateResponse` calls across `calm.py` (6 endpoints) and `tools.py` (1 endpoint) to use the new Starlette 1.0.0 API. **Result:** `tox -e unit` passes with 3242 passed, 0 failed.
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 seed:serve-real
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#1112
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?