Skip to content

Database connection behaviour

active 2025-03-062026-07-06 (UTC)

Partial coverage12,431 / 14,140 hourly files (88%) · 2 absent upstream · 1,703 failed, retryable2024-12-292026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
92
Pushes
24
Pull requests
6
Issues
3
Stars
22
Forks
1

Activity over time

Daily event counts in the loaded window

Line chart, 488 days from 2025-03-06 to 2026-07-06. Pushes: 24 total, peak 4 in a day. Pull requests: 6 total, peak 1 in a day. Issues: 3 total, peak 1 in a day. Comments: 24 total, peak 3 in a day. Stars: 22 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
josevalim352018
greg-rychlewski8213
nathanl7023
v0idpwn3201
pepicrft2002
DVSLabs2001
realglebivanov2002
mtrudel1010
kianmeng1001
guisehn1010
Schultzer1001
luigi-discoup1001
wojtekmach1001

Recent activity

Latest issues, pull requests and releases

  • Issue comment#343v0idpwn2026-04-20 18:43
    Fix Watcher blocking during slow pool termination
  • Issue comment#341kianmeng2026-03-06 02:57
    Support Elixir 1.19/OTP 28 and bump actions
  • Issue#340josevalim2026-02-10 07:47
    credential leak when no_more_pool exit are raised
  • Issue comment#336Schultzer2026-01-24 15:16
    Remove sensitive options before calling after_connect
  • Issue comment#339greg-rychlewski2026-01-13 21:57
    add `checkout_retries` to start options
  • Issue comment#332nathanl2025-11-25 21:09
    Put a label (like Repo name) in these errors
  • Issue comment#338nathanl2025-11-13 18:56
    More label usage
  • Issue comment#338josevalim2025-11-13 06:34
    More label usage
  • Issue comment#337josevalim2025-11-09 12:03
    Allow client to reconnect when specified
  • Pull request#337josevalim2025-11-09 12:01
  • Issue comment#329josevalim2025-11-09 10:13
    Closed connections only reconnected after ping
  • Issue comment#329greg-rychlewski2025-11-09 06:51
    Closed connections only reconnected after ping
  • Issue comment#335luigi-discoup2025-11-06 16:48
    Sensitive data printed despite the `show_sensitive_data_on_connection_error: false` flag
  • Issue comment#335greg-rychlewski2025-11-06 12:16
    Sensitive data printed despite the `show_sensitive_data_on_connection_error: false` flag
  • Issue#335greg-rychlewski2025-11-06 12:13
    Sensitive data printed despite the `show_sensitive_data_on_connection_error: false` flag
  • Pull request#336greg-rychlewski2025-11-06 04:44
  • Issue comment#332realglebivanov2025-11-03 17:20
    Put the repo name in these errors
  • Issue comment#332realglebivanov2025-11-01 23:03
    Put the repo name in these errors
  • Issue comment#332josevalim2025-10-30 07:23
    Put the repo name in these errors
  • Pull request#334guisehn2025-10-29 23:05
  • Pull request#332nathanl2025-10-28 13:28
  • Issue comment#331josevalim2025-10-22 22:09
    Show pool mode in this error
  • Pull request#330nathanl2025-09-09 14:09
  • Issue comment#329DVSLabs2025-07-07 10:44
    Closed connections only reconnected after ping
  • Issue#329DVSLabs2025-07-07 07:52
    Closed connections only reconnected after ping

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.