active 2024-01-12 → 2024-07-30 (UTC)
Complete coverage26,546 / 26,546 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-08-25 (UTC)
Events
15
Pushes
3
Pull requests
0
Issues
5
Stars
0
Forks
0
Activity over time
Daily event counts in the loaded window
Line chart, 201 days from 2024-01-12 to 2024-07-30. Pushes: 3 total, peak 1 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 5 total, peak 3 in a day. Comments: 7 total, peak 2 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| boredzo | 15 | 3 | 0 | 7 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#14boredzo2024-07-30 05:44Sometimes the last mebibyte doesn't get copied on a single-core machine
- Issue comment#14boredzo2024-01-15 06:38Sometimes the last mebibyte doesn't get copied on a single-core machine
- Issue comment#14boredzo2024-01-14 05:12Sometimes the last mebibyte doesn't get copied on a single-core machine
- Issue comment#14boredzo2024-01-13 03:03Sometimes the last mebibyte doesn't get copied on a single-core machine
- Issue comment#14boredzo2024-01-13 02:54Sometimes the last mebibyte doesn't get copied on a single-core machine
- Issue#14boredzo2024-01-13 02:49Sometimes the last mebibyte doesn't get copied on a single-core machine
- Issue#13boredzo2024-01-13 02:41POSIX port should use F_RDAHEAD and F_NOCACHE when available
- Issue#13boredzo2024-01-12 22:56POSIX port should use F_RDAHEAD and F_NOCACHE when available
- Issue#12boredzo2024-01-12 21:40dd-parallel-posix occasionally corrupts data
- Issue comment#12boredzo2024-01-12 21:37dd-parallel-posix occasionally corrupts data
- Issue comment#12boredzo2024-01-12 21:35dd-parallel-posix occasionally corrupts data
- Issue#12boredzo2024-01-12 21:34dd-parallel-posix occasionally corrupts data
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.