Skip to content

BugSnag error monitoring & reporting software for rails, sinatra, rack and ruby

active 2023-08-172026-06-14 (UTC)

Complete coverage26,469 / 26,469 hourly files (100%) · 2 absent upstream2023-08-152026-08-21 (UTC)
Events
473
Pushes
145
Pull requests
59
Issues
20
Stars
22
Forks
12

Activity over time

Daily event counts in the loaded window

Line chart, 1033 days from 2023-08-17 to 2026-06-14. Pushes: 145 total, peak 18 in a day. Pull requests: 59 total, peak 5 in a day. Issues: 20 total, peak 2 in a day. Comments: 104 total, peak 14 in a day. Stars: 22 total, peak 1 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

Recent activity

Latest issues, pull requests and releases

  • Pull request#853twometresteve2026-01-21 13:03
  • Pull request#852twometresteve2026-01-21 11:08
  • Pull request#848twometresteve2026-01-12 10:56
  • Pull request#847twometresteve2026-01-08 21:07
  • Issue#846agrzegorzewski2025-12-29 12:34
    Errors during rails (env) configuration generate a confusing Bugsnag error with embedded Bugsnag trackeback
  • Issue comment#846agrzegorzewski2025-12-29 12:34
    Errors during rails (env) configuration generate a confusing Bugsnag error with embedded Bugsnag trackeback
  • Issue#846timdiggins2025-12-21 15:55
    Errors during rails (env) configuration generate a confusing Bugsnag error with embedded Bugsnag trackeback
  • Issue comment#725YesThatAllen2025-10-05 21:14
    Error Message: "Not delivering sessions due to an invalid api_key" needs to clarify it's coming from Bugsnag Gem
  • Pull request#842twometresteve2025-07-08 10:05
  • Releasetwometresteve2025-07-08 10:02
    v6.28.0
  • Pull request#840twometresteve2025-07-07 18:00
  • Pull request#839twometresteve2025-06-11 12:04
  • Pull request#838twometresteve2025-06-11 12:00
  • Issue comment#837twometresteve2025-06-11 11:54
    Fix/skip failing tests
  • Pull request#837twometresteve2025-06-11 11:54
  • Pull request#835twometresteve2025-06-03 09:52
  • Issue comment#801clr1822025-05-21 09:59
    Mongo breadcrumb: Do not mask filter value nil
  • Issue comment#801johnnyshields2025-05-17 13:05
    Mongo breadcrumb: Do not mask filter value nil
  • Pull request#831tgwizard2025-05-14 14:29
  • Issue comment#90bogdan2025-04-02 08:32
    Allow to notify about sidekiq error only after several insuccessful retries
  • Issue comment#831mclack2025-03-24 14:44
    Switch to ActiveSupport::Notifications.monotonic_subscribe
  • Issue comment#831tgwizard2025-03-21 08:58
    Switch to ActiveSupport::Notifications.monotonic_subscribe
  • Pull request#834mclack2025-03-18 09:16
  • Issue comment#833mclack2025-03-14 11:16
    Mutex does not isolate threads
  • Issue#833mclack2025-03-14 11:16
    Mutex does not isolate threads

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