Skip to content

Record Router

active 2024-04-172025-12-19 (UTC)

Complete coverage26,775 / 26,775 hourly files (100%) · 2 absent upstream2023-08-152026-09-03 (UTC)
Events
59
Pushes
1
Pull requests
8
Issues
8
Stars
1
Forks
2

Activity over time

Daily event counts in the loaded window

Line chart, 612 days from 2024-04-17 to 2025-12-19. Pushes: 1 total, peak 1 in a day. Pull requests: 8 total, peak 5 in a day. Issues: 8 total, peak 4 in a day. Comments: 33 total, peak 21 in a day. Stars: 1 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

ContributorContributionsPushesPRsComments
StrongestNumber9451331
kortemik5032
dependabot[bot]2020
ronja-ui1000

Recent activity

Latest issues, pull requests and releases

  • Pull request#15dependabot[bot]2025-12-19 23:24
  • Pull request#15dependabot[bot]2025-12-19 23:24
  • Issue#13ronja-ui2025-04-08 06:51
    Add PR template
  • Issue comment#10StrongestNumber92024-10-14 11:50
    Flooding using rlp_10 occasionally causes Cannot return wrapped ByteBuffer, BufferLease phaser was already terminated!
  • Issue#12StrongestNumber92024-10-14 11:50
    Cannot return wrapped ByteBuffer, BufferLease phaser was already terminated
  • Issue#11StrongestNumber92024-09-26 13:49
    EmptyTagTest throws occasionally for IndexOutOfBoundsException when file based log4j2 xml is used
  • Issue comment#5StrongestNumber92024-09-26 09:44
    Accepting new connections gets stuck after too many threads have disconnected uncleanly
  • Issue comment#5StrongestNumber92024-09-26 09:20
    Accepting new connections gets stuck after too many threads have disconnected uncleanly
  • Issue comment#5kortemik2024-09-25 14:24
    Accepting new connections gets stuck after too many threads have disconnected uncleanly
  • Issue comment#5kortemik2024-09-25 14:22
    Accepting new connections gets stuck after too many threads have disconnected uncleanly
  • Issue comment#9StrongestNumber92024-09-25 13:51
    upgrade to rlp_03 version 8
  • Pull request#9kortemik2024-09-25 13:14
  • Issue comment#8StrongestNumber92024-07-04 07:03
    Connection count in statistics keeps on getting higher when connections fail (or connections get leaked)
  • Issue comment#5StrongestNumber92024-07-03 14:43
    Accepting new connections gets stuck after too many threads have disconnected uncleanly
  • Issue comment#8StrongestNumber92024-07-03 07:33
    Connection count in statistics keeps on getting higher when connections fail
  • Issue comment#7StrongestNumber92024-07-02 12:54
    Timeout settings do not seem to be used at all
  • Issue#7StrongestNumber92024-07-02 12:54
    Timeout settings do not seem to be used at all
  • Issue#8StrongestNumber92024-07-02 12:06
    Connection count in statistics keeps on getting higher when connections fail
  • Issue#7StrongestNumber92024-07-02 11:57
    Timeout settings do not seem to be used at all
  • Issue comment#5StrongestNumber92024-07-02 10:38
    Accepting new connections gets stuck after too many threads have disconnected uncleanly
  • Issue comment#5StrongestNumber92024-07-02 10:28
    Accepting new connections gets stuck after too many threads have disconnected uncleanly
  • Issue#6StrongestNumber92024-07-02 09:25
    Responses are not checked for RSP status 500
  • Issue comment#5StrongestNumber92024-07-02 08:24
    Accepting new connections gets stuck after too many threads have disconnected uncleanly
  • Issue comment#5StrongestNumber92024-07-01 14:23
    Accepting new connections gets stuck after too many threads have disconnected uncleanly
  • Issue comment#5StrongestNumber92024-07-01 13:49
    Accepting new connections gets stuck after too many threads have disconnected uncleanly

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