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

[CRITICAL] Event system has 0% test coverage #45

New Issue
Closed
opened 2026-03-14 18:46:36 +00:00 by kimi · 0 comments
kimi commented 2026-03-14 18:46:36 +00:00
Collaborator
Copy Link

Problem

The infrastructure event system (pub/sub backbone) has 0% test coverage:

  • infrastructure/events/bus.py - 74 lines, 0% coverage
  • infrastructure/events/broadcaster.py - 67 lines, 0% coverage
  • infrastructure/error_capture.py - 91 lines, 0% coverage

This is critical infrastructure that handles all inter-component communication. A bug here could cause silent failures across the entire system.

Impact

  • Event bus failures would not be caught by CI
  • Memory leaks in event handlers undetected
  • Error capture/reporting blind spot

Acceptance Criteria

  • Add tests for event_bus singleton (subscribe, publish, unsubscribe)
  • Add tests for wildcard pattern matching
  • Add tests for event persistence (WAL mode)
  • Add tests for error capture/reporting functionality
  • Achieve ≥80% coverage on all three modules
  • Test edge cases: handler exceptions, unsubscribe non-existent, memory limits

Priority: CRITICAL 🔴

## Problem The infrastructure event system (pub/sub backbone) has **0% test coverage**: - `infrastructure/events/bus.py` - 74 lines, 0% coverage - `infrastructure/events/broadcaster.py` - 67 lines, 0% coverage - `infrastructure/error_capture.py` - 91 lines, 0% coverage This is critical infrastructure that handles all inter-component communication. A bug here could cause silent failures across the entire system. ## Impact - Event bus failures would not be caught by CI - Memory leaks in event handlers undetected - Error capture/reporting blind spot ## Acceptance Criteria - [ ] Add tests for `event_bus` singleton (subscribe, publish, unsubscribe) - [ ] Add tests for wildcard pattern matching - [ ] Add tests for event persistence (WAL mode) - [ ] Add tests for error capture/reporting functionality - [ ] Achieve ≥80% coverage on all three modules - [ ] Test edge cases: handler exceptions, unsubscribe non-existent, memory limits ## Priority: CRITICAL 🔴
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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