active 2023-11-12 → 2023-11-30 (UTC)
Complete coverage26,722 / 26,722 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-09-01 (UTC)
Events
9
Pushes
1
Pull requests
0
Issues
1
Stars
1
Forks
0
Activity over time
Daily event counts in the loaded window
Line chart, 19 days from 2023-11-12 to 2023-11-30. Pushes: 1 total, peak 1 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 1 total, peak 1 in a day. Comments: 6 total, peak 3 in a day. Stars: 1 total, peak 1 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 |
|---|---|---|---|---|
| dizcza | 5 | 1 | 0 | 4 |
| GraceZhuuu | 3 | 0 | 0 | 2 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#1dizcza2023-11-30 07:12RuntimeError: indices should be either on cpu or on the same device as the indexed tensor (cpu)
- Issue comment#1dizcza2023-11-30 07:11RuntimeError: indices should be either on cpu or on the same device as the indexed tensor (cpu)
- Issue comment#1GraceZhuuu2023-11-30 06:47RuntimeError: indices should be either on cpu or on the same device as the indexed tensor (cpu)
- Issue comment#1dizcza2023-11-27 09:22RuntimeError: indices should be either on cpu or on the same device as the indexed tensor (cpu)
- Issue comment#1GraceZhuuu2023-11-27 09:04RuntimeError: indices should be either on cpu or on the same device as the indexed tensor (cpu)
- Issue#1GraceZhuuu2023-11-27 09:04RuntimeError: indices should be either on cpu or on the same device as the indexed tensor (cpu)
- Issue comment#1dizcza2023-11-27 08:56RuntimeError: indices should be either on cpu or on the same device as the indexed tensor (cpu)
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 1 stars here means stars gained during the window, not the repo's star count.