Rust Client library for Apache Pulsar
active 2025-04-06 → 2026-06-26 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 447 days from 2025-04-06 to 2026-06-26. Pushes: 47 total, peak 7 in a day. Pull requests: 29 total, peak 3 in a day. Issues: 19 total, peak 2 in a day. Comments: 76 total, peak 12 in a day. Stars: 19 total, peak 2 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 |
|---|---|---|---|---|
| BewareMyPower | 93 | 33 | 14 | 21 |
| Copilot | 27 | 0 | 0 | 14 |
| ChrisWrenDev | 25 | 0 | 4 | 17 |
| chamons | 14 | 0 | 0 | 10 |
| codelipenghui | 13 | 9 | 1 | 1 |
| crossoverJie | 10 | 0 | 1 | 3 |
| darinspivey | 5 | 0 | 2 | 2 |
| streamnativebot | 4 | 4 | 0 | 0 |
| PookieBuns | 4 | 0 | 2 | 1 |
| kaustubh-garimella-genius | 3 | 0 | 0 | 1 |
| dylankyc | 2 | 0 | 0 | 0 |
| LorenzoTettamanti | 2 | 0 | 2 | 0 |
| dsferruzza | 2 | 0 | 0 | 1 |
| chatgpt-codex-connector[bot] | 1 | 0 | 0 | 0 |
| jr011 | 1 | 0 | 1 | 0 |
| dispatcherx | 1 | 0 | 0 | 1 |
| jiangpengcheng | 1 | 1 | 0 | 0 |
| meten-natuurlijk | 1 | 0 | 0 | 0 |
| pomacanthidae | 1 | 0 | 1 | 0 |
| mattsre | 1 | 0 | 1 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue#414PookieBuns2026-05-27 01:44Consumer stream hangs after namespace unload
- Issue#408BewareMyPower2026-05-21 01:47Pong responses discarded under high load, causing broker to kill connections
- Pull request#409PookieBuns2026-04-11 12:36
- Pull request#409PookieBuns2026-04-10 22:42
- Issue#405BewareMyPower2026-03-30 03:01Can we cut a new numbered release?
- Issue comment#399BewareMyPower2026-03-16 06:12feat: support external schema registry (PIP-420)
- Pull request#398codelipenghui2026-03-12 03:03
- Issue comment#397PookieBuns2026-02-28 00:17fix: Preserve message metadata when sending to DLQ
- Pull request#396darinspivey2026-02-24 13:41
- Pull request#395BewareMyPower2026-02-24 10:49
- Pull request#395BewareMyPower2026-02-24 09:54
- Issue comment#390darinspivey2026-01-30 22:06fix(consumer): `update_topics` should only log if topics are recreated
- Pull request#390darinspivey2026-01-30 21:45
- Issue#389darinspivey2026-01-30 21:15Logging is too noisy for multi `update_topics`
- Pull request#388jr0112026-01-25 09:36
- Issue comment#387darinspivey2026-01-14 20:02fix: prevent check_connections from dropping connections during setup
- Issue comment#384chamons2026-01-09 22:11fix: Correctly handle consumer errors and removal due to pulsar cluster restarts by unconditionally update_topics in MultiTopicConsumer
- Pull request#382pomacanthidae2026-01-07 12:21
- Pull request#383LorenzoTettamanti2026-01-07 00:49
- Issue comment#378chamons2025-12-30 15:25Topic load shedding causes Producers (including built in one in connection object) to fail until you manually close them after error
- Pull request#380mattsre2025-12-30 06:40
- Issue comment#378BewareMyPower2025-12-30 02:51Topic load shedding causes Producers (including built in one in connection object) to fail until you manually close them after error
- Issue#375chamons2025-12-26 15:39Consumer polling errors (such as restarting pulsar brokers) can cause MultiTopicConsumer to silently drop topics from consumption
- Issue comment#375chamons2025-12-23 17:15Consumer polling errors (such as restarting pulsar brokers) can cause MultiTopicConsumer to silently drop topics from consumption
- Pull request#377BewareMyPower2025-12-17 13:53
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 19 stars here means stars gained during the window, not the repo's star count.