A timer running a callback in a specified interval
active 2023-12-18 → 2025-08-22 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 614 days from 2023-12-18 to 2025-08-22. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 2 total, peak 1 in a day. Comments: 5 total, peak 2 in a day. Stars: 6 total, peak 1 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 |
|---|---|---|---|---|
| flyte | 3 | 0 | 0 | 2 |
| eirikskogoy | 2 | 0 | 0 | 1 |
| inf0rmatix | 2 | 0 | 0 | 2 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#7inf0rmatix2024-09-11 14:09High CPU usage
- Issue comment#7eirikskogoy2024-08-07 05:11High CPU usage
- Issue comment#8flyte2024-08-05 16:15When resuming timer after stopping it, the elapsed ms includes the period over which it was stopped.
- Issue#8flyte2024-08-05 16:07When resuming timer after stopping it, the elapsed ms includes the period over which it was stopped.
- Issue comment#7flyte2024-08-05 16:04High CPU usage
- Issue comment#7inf0rmatix2024-06-14 07:31High CPU usage
- Issue#7eirikskogoy2024-06-11 11:58High CPU usage
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 6 stars here means stars gained during the window, not the repo's star count.