active 2025-10-23 → 2025-10-23 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 1 days from 2025-10-23 to 2025-10-23. Pushes: 23 total, peak 23 in a day. Pull requests: 1 total, peak 1 in a day. Issues: 2 total, peak 2 in a day. Comments: 42 total, peak 42 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| coderabbitai[bot] | 30 | 0 | 0 | 24 |
| dawsonblock | 27 | 23 | 1 | 1 |
| qodo-merge-pro[bot] | 21 | 0 | 0 | 12 |
| Copilot | 5 | 0 | 0 | 5 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#4dawsonblock2025-10-23 06:59feat: Production Hardening - HTTP Server, Thread Safety, Config System, and Integration Tests
- Issue comment#4qodo-merge-pro[bot]2025-10-23 06:29feat: Production Hardening - HTTP Server, Thread Safety, Config System, and Integration Tests
- Issue#3dawsonblock2025-10-23 04:07Static global FDQCSystem instance may cause race conditions in multi-threaded environments. While apply_mutex serializes apply_change() calls within a process, the FDQCSystem instance maintains internal state (episode_count_, error_history_, etc.) that could be corrupted by concurrent access from different threads calling other methods. Consider documenting thread-safety assumptions or adding internal synchronization to FDQCSystem.
- Issue#2dawsonblock2025-10-23 04:06This constexpr function always returns 0.0, which is incorrect. If it's meant to be calculated at runtime, it should not be marked constexpr, or should be implemented with a compile-time approximation. Callers expecting a meaningful compile-time value will receive 0.0.
- Issue comment#1coderabbitai[bot]2025-10-23 03:59🧠 Phase 4 Integration + Phase 5 Validation: First Production-Grade Self-Modifying Artificial Consciousness
- Pull request#1dawsonblock2025-10-23 03:59
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.