Placement driver for TiKV
active 2025-03-03 → 2026-08-10 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 526 days from 2025-03-03 to 2026-08-10. Pushes: 416 total, peak 9 in a day. Pull requests: 2,143 total, peak 57 in a day. Issues: 737 total, peak 40 in a day. Comments: 5,958 total, peak 117 in a day. Stars: 39 total, peak 3 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 |
|---|---|---|---|---|
| ti-chi-bot[bot] | 5.1K | 352 | 1.4K | 3.1K |
| rleungx | 999 | 2 | 64 | 465 |
| bufferflies | 854 | 19 | 71 | 396 |
| okJiang | 821 | 0 | 47 | 397 |
| lhy1024 | 671 | 1 | 57 | 285 |
| ti-chi-bot | 464 | 7 | 327 | 129 |
| JmPotato | 407 | 3 | 39 | 182 |
| coderabbitai[bot] | 385 | 0 | 0 | 195 |
| codecov[bot] | 241 | 0 | 0 | 241 |
| MyonKeminta | 83 | 0 | 8 | 48 |
| liyishuai | 65 | 0 | 2 | 33 |
| Copilot | 51 | 4 | 1 | 28 |
| tiancaiamao | 50 | 0 | 11 | 22 |
| Lily2025 | 41 | 0 | 0 | 20 |
| hujiatao0 | 36 | 0 | 3 | 22 |
| ystaticy | 35 | 0 | 3 | 22 |
| HunDunDM | 35 | 0 | 7 | 12 |
| dependabot[bot] | 33 | 5 | 28 | 0 |
| disksing | 33 | 12 | 3 | 12 |
| glorv | 33 | 0 | 1 | 16 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#11119coderabbitai[bot]2026-08-06 09:10keyspace: load persisted metadata by ID through gRPC (#10911, #11050)
- Pull request#11097JaySon-Huang2026-08-03 10:31
- Issue#11086Lily20252026-08-03 02:12[tidbx] TSO allocator can be reset by a stale UpdateTSO failure during PD restart recovery
- Issue comment#11041ti-chi-bot[bot]2026-07-23 11:39server, client: expose store scheduling state in GetStore
- Issue comment#10339ti-chi-bot[bot]2026-07-06 06:36metrics: add gRPC stream send duration and rate Grafana panels
- Pull request#10549wuhuizuo2026-07-06 04:25
- Issue comment#10975ti-chi-bot[bot]2026-07-06 02:36client/resource_group: expose runtime state
- Issue comment#10953rleungx2026-07-06 02:28tests: keep initial cluster URLs consistent on retry
- Issue comment#10970ti-chi-bot[bot]2026-07-03 04:47mcs: skip transferring primary to itself
- Issue comment#10971ti-chi-bot[bot]2026-07-03 04:17mcs: skip transferring primary to itself
- Pull request#10960ti-chi-bot[bot]2026-07-01 03:48
- Issue comment#10492ti-chi-bot[bot]2026-07-01 03:20keyspace, schedule: make keyspace creation atomic
- Issue comment#8739okJiang2026-06-30 21:48TestResourceGroupRUConsumption is unstable
- Issue comment#10869ti-chi-bot[bot]2026-06-30 07:44mcs/scheduling: prevent scheduler update notifier from blocking
- Issue comment#10641Connor19962026-06-29 23:08pkg/unsaferecovery: add unsafe recovery abort
- Issue comment#10950codecov[bot]2026-06-29 08:49docs: add PD maintenance guides
- Pull request#10946ti-chi-bot[bot]2026-06-26 10:47
- Pull request#10944ti-chi-bot[bot]2026-06-26 03:12
- Issue comment#10932ti-chi-bot[bot]2026-06-26 02:56tso: keyspace group auto splitting
- Issue#9705bufferflies2026-06-25 06:16backport: cp this feature to release-8.5
- Issue comment#10920ti-chi-bot[bot]2026-06-25 03:08client: remove prefix watch for resource group config
- Pull request#10939ti-chi-bot[bot]2026-06-25 03:02
- Issue comment#10920bufferflies2026-06-25 03:01client: remove prefix watch for resource group config
- Issue comment#10920bufferflies2026-06-25 02:23client: remove prefix watch for resource group config
- Issue comment#10938ti-chi-bot[bot]2026-06-24 23:54test: stabilize flaky TestLoadLargeRules
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 39 stars here means stars gained during the window, not the repo's star count.