⚡ High-performance job queue for Bun. SQLite persistence, DLQ, cron jobs, S3 backups. Built for AI agents and automation
active 2026-01-28 → 2026-08-26 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 211 days from 2026-01-28 to 2026-08-26. Pushes: 292 total, peak 59 in a day. Pull requests: 3 total, peak 2 in a day. Issues: 30 total, peak 5 in a day. Comments: 43 total, peak 7 in a day. Stars: 117 total, peak 36 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 |
|---|---|---|---|---|
| egeominotti | 323 | 292 | 1 | 17 |
| arthurvanl | 24 | 0 | 0 | 11 |
| coderabbitai[bot] | 14 | 0 | 0 | 7 |
| nightire | 3 | 0 | 0 | 2 |
| motopods | 2 | 0 | 0 | 1 |
| jdorner | 2 | 0 | 0 | 2 |
| simontong | 2 | 0 | 2 | 0 |
| Tiaansu | 1 | 0 | 0 | 0 |
| timnew | 1 | 0 | 0 | 1 |
| vercel[bot] | 1 | 0 | 0 | 1 |
| cbsmith402 | 1 | 0 | 0 | 0 |
| yuri-kapta | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#94egeominotti2026-06-07 11:16Worker never recovers from a half-open TCP connection (Command-timeout loop, no reconnect)
- Issue#94egeominotti2026-06-07 10:24Worker never recovers from a half-open TCP connection (Command-timeout loop, no reconnect)
- Issue#92egeominotti2026-06-04 23:362.8.3: getFailedAsync() returns empty for a failed job (standalone server); pause() double-counts instead of moving waiting→paused
- Issue#93egeominotti2026-06-04 23:36`bunqueue/client` is unusable from Node despite engines.node >=18: ERR_UNSUPPORTED_DIR_IMPORT on import, and Bun-only globals in the TCP transport (2.8.3)
- Issue comment#92egeominotti2026-06-04 23:362.8.3: getFailedAsync() returns empty for a failed job (standalone server); pause() double-counts instead of moving waiting→paused
- Issue comment#86arthurvanl2026-05-27 12:41Attempts field is ignored when job fails
- Issue comment#85timnew2026-05-11 07:59Failed to start Server
- Issue comment#84jdorner2026-04-21 06:18queue.cleanAsync() does not remove completed jobs
- Releasegithub-actions[bot]2026-04-20 16:21Release v2.7.10
- Issue comment#84jdorner2026-04-20 12:08queue.cleanAsync() does not remove completed jobs
- Releasegithub-actions[bot]2026-04-20 11:02Release v2.7.9
- Issue comment#84egeominotti2026-04-19 22:20queue.cleanAsync() does not remove completed jobs
- Issue comment#84egeominotti2026-04-19 22:20queue.cleanAsync() does not remove completed jobs
- Releasegithub-actions[bot]2026-04-12 19:40Release v2.7.3
- Releasegithub-actions[bot]2026-04-10 20:56Release v2.8.0
- Issue comment#77egeominotti2026-04-10 09:24new queue parameter that skips certain scheduled keys
- Issue#80egeominotti2026-04-09 20:43Deduplication not working for long-running scheduled jobs in Simple Mode & inconsistent execution interval
- Releasegithub-actions[bot]2026-04-03 16:31Release v2.6.113
- Issue#74arthurvanl2026-04-03 07:17Stacktrace not included in `failed` worker event
- Issue#74arthurvanl2026-04-03 07:17Stacktrace not included in `failed` worker event
- Releasegithub-actions[bot]2026-04-03 00:26Release v2.6.109
- Issue comment#73egeominotti2026-04-02 15:34Queue#upsertScheduler starts right away....
- Issue comment#73egeominotti2026-04-02 15:27Queue#upsertScheduler starts right away....
- Issue comment#73arthurvanl2026-04-02 13:06Queue#upsertScheduler starts right away....
- Issue comment#73egeominotti2026-04-02 13:04Queue#upsertScheduler starts right away....
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 117 stars here means stars gained during the window, not the repo's star count.