Stack structure done by me.
active 2024-09-26 → 2025-03-01 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 157 days from 2024-09-26 to 2025-03-01. Pushes: 21 total, peak 6 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 10 total, peak 4 in a day. Comments: 12 total, peak 8 in a day. Stars: 2 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 |
|---|---|---|---|---|
| Barkir | 30 | 21 | 0 | 8 |
| Raptor-X102 | 8 | 0 | 0 | 4 |
| doushe821 | 5 | 0 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#7Raptor-X1022024-10-09 05:26Double Ctor call leads to memory leak
- Issue comment#10Barkir2024-10-09 05:26no stk null pointer check (segfault in main)
- Issue comment#9Barkir2024-10-09 05:25Ctor segfault, stack null pointer (proove = no cosole output)
- Issue comment#7Barkir2024-10-09 05:24Double Ctor call leads to memory leak
- Issue comment#8Raptor-X1022024-10-09 05:23Undefined behaviour, no stack limit check
- Issue comment#8Barkir2024-10-09 05:23Undefined behaviour, no stack limit check
- Issue comment#8Barkir2024-10-09 05:23Undefined behaviour, no stack limit check
- Issue comment#8Barkir2024-10-09 05:17Undefined behaviour, no stack limit check
- Issue comment#10Raptor-X1022024-10-08 20:20no stk null pointer check (segfault in main)
- Issue#10Raptor-X1022024-10-08 20:20no stk null pointer check (segfault in main)
- Issue#9Raptor-X1022024-10-08 20:19Ctor segfault, stack null pointer (proove = no cosole output)
- Issue#8Raptor-X1022024-10-08 20:19Undefined behaviour, no stack limit check
- Issue comment#7Raptor-X1022024-10-08 20:18Double Ctor call leads to memory leak
- Issue#7Raptor-X1022024-10-08 20:18Double Ctor call leads to memory leak
- Issue#6doushe8212024-10-07 19:46Static hash variable prevents working with multuple stacks
- Issue#5doushe8212024-10-07 19:33Hash doesn't consider size changes, which can lead to segm fault as in example (resize doubles data size, which still isnt enough)
- Issue comment#1Barkir2024-10-07 12:34Seg Fault if init capacity is too large
- Issue comment#4Barkir2024-10-07 12:33Stack hash doesnt detect size changes
- Issue#4Barkir2024-10-07 12:33Stack hash doesnt detect size changes
- Issue#4doushe8212024-10-04 19:48Stack hash doesnt detect size changes
- Issue#3doushe8212024-10-04 19:30No negative capacity check (segm fault)
- Issue#1doushe8212024-10-04 18:55Seg Fault if init capacity is too large
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 2 stars here means stars gained during the window, not the repo's star count.