Proof-of concept for a method of creating and identifying critical sections such that they can be statically analysed for violations
active 2024-04-22 → 2024-04-24 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 3 days from 2024-04-22 to 2024-04-24. Pushes: 2 total, peak 1 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 3 total, peak 2 in a day. Comments: 0 total, peak 0 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 |
|---|---|---|---|---|
| JetSetIlly | 5 | 2 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue#3JetSetIlly2024-04-23 09:08Analysistest package
- Issue#2JetSetIlly2024-04-23 09:06Leasing the wrong critical section
- Issue#1JetSetIlly2024-04-22 21:25"Start of violation" incorrect in some cases
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.