Skip to content

resque/resque-unique_at_runtime

View on GitHub ↗Related repositories →

A resque plugin that ensures that only one job for a given queue will be running on any worker at a given time.

active 2024-08-262026-01-17 (UTC)

Complete coverage26,530 / 26,530 hourly files (100%) · 2 absent upstream2023-08-152026-08-24 (UTC)
Events
19
Pushes
3
Pull requests
3
Issues
2
Stars
4
Forks
1

Activity over time

Daily event counts in the loaded window

Line chart, 510 days from 2024-08-26 to 2026-01-17. Pushes: 3 total, peak 2 in a day. Pull requests: 3 total, peak 2 in a day. Issues: 2 total, peak 1 in a day. Comments: 2 total, peak 1 in a day. Stars: 4 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

ContributorContributionsPushesPRsComments
pboling8311
jiikko3020
seeronline1001

Recent activity

Latest issues, pull requests and releases

  • Pull request#195pboling2024-09-05 20:23
  • Issue#194pboling2024-09-05 20:22
    Multiple Executions Due to Error-Induced Double Unlock
  • Issue comment#194pboling2024-09-05 20:19
    Multiple Executions Due to Error-Induced Double Unlock
  • Pull request#196jiikko2024-08-27 04:25
  • Pull request#195jiikko2024-08-27 02:05
  • Issue comment#194seeronline2024-08-26 07:36
    Multiple Executions Due to Error-Induced Double Unlock
  • Issue#194jiikko2024-08-26 07:36
    Multiple Executions Due to Error-Induced Double Unlock

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