Skip to content

ruby-concurrency/concurrent-ruby

View on GitHub ↗Related repositories →

Modern concurrency tools including agents, futures, promises, thread pools, supervisors, and more. Inspired by Erlang, Clojure, Scala, Go, Java, JavaScript, and classic concurrency patterns.

active 2025-01-182026-06-20 (UTC)

Partial coverage12,095 / 13,665 hourly files (89%) · 2 absent upstream · 1,566 failed, retryable2025-01-182026-08-10 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
177
Pushes
16
Pull requests
16
Issues
7
Stars
69
Forks
6

Activity over time

Daily event counts in the loaded window

Line chart, 519 days from 2025-01-18 to 2026-06-20. Pushes: 16 total, peak 2 in a day. Pull requests: 16 total, peak 4 in a day. Issues: 7 total, peak 3 in a day. Comments: 37 total, peak 3 in a day. Stars: 69 total, peak 4 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

ContributorContributionsPushesPRsComments
eregon311247
bensheldon21239
joshuay0316238
barracuda1568014
trinistr3002
mrj2001
nobu2020
forthrin2002
snickell1001
Hungor1001
byroot1001
wwahammy1010
dependabot[bot]1010
joceyall30-cell1000
SamSaffron1001
gongfarmer1000
meineerde1010

Recent activity

Latest issues, pull requests and releases

  • Pull request#1105joshuay032026-06-14 03:04
  • Issue#1103joceyall30-cell2026-05-05 03:54
    NO Third party 🥳
  • Issue comment#1099eregon2026-02-22 11:38
    Deadlock race when calling ScheduledTask#reschedule
  • Issue comment#1099bensheldon2026-02-09 02:32
    Deadlock race when calling ScheduledTask#reschedule
  • Issue comment#1099snickell2026-02-04 06:10
    Deadlock race when calling ScheduledTask#reschedule
  • Issue#1063eregon2026-01-11 18:12
    atomic_reference.c fails to compile on 32-bit due to unconditional usage of 64-bit atomics
  • Pull request#1064barracuda1562026-01-11 18:12
  • Issue comment#1064barracuda1562026-01-08 02:14
    concurrent-ruby-ext: fix build on Darwin 32-bit
  • Issue comment#1064eregon2026-01-07 14:51
    concurrent-ruby-ext: fix build on Darwin 32-bit
  • Issue comment#1032bensheldon2025-12-11 05:04
    Add API to prestart threads in threadpools
  • Pull request#1098bensheldon2025-12-11 04:38
  • Pull request#1044bensheldon2025-12-10 22:38
  • Issue#662bensheldon2025-12-10 22:38
    shutdown/execute timertask will generate one more thread run the same task
  • Issue comment#662bensheldon2025-12-10 22:38
    shutdown/execute timertask will generate one more thread run the same task
  • Issue#672bensheldon2025-12-10 22:37
    shutdown and execute a timertask results in double runs
  • Pull request#1001bensheldon2025-12-10 22:37
  • Issue comment#1001eregon2025-12-10 21:08
    Allow TimerTask to be safely restarted after shutdown and avoid duplicate tasks
  • Issue#1069eregon2025-12-10 20:51
    Should RubySingleThreadExecutor be marked to be a SerialExecutorService again?
  • Pull request#1070meineerde2025-12-10 20:51
  • Issue comment#1082joshuay032025-12-10 10:27
    Asynchronous pruning for RubyThreadPoolExecutor
  • Pull request#1097eregon2025-12-10 10:10
  • Pull request#1096nobu2025-12-08 23:32
  • Issue comment#1095eregon2025-12-08 19:58
    Implement FIFO and LRU caches through a Map memory limit
  • Issue comment#1095byroot2025-12-08 19:11
    Implement FIFO and LRU caches through a Map memory limit
  • Issue comment#1095mrj2025-12-08 17:32
    Implement FIFO and LRU caches through a Map memory limit

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 69 stars here means stars gained during the window, not the repo's star count.