Skip to content

TransactionProcessing/FileProcessor

View on GitHub ↗Related repositories →

active 2024-12-012026-08-09 (UTC)

Partial coverage12,877 / 14,856 hourly files (87%) · 2 absent upstream · 1,973 failed, retryable2024-11-302026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
407
Pushes
57
Pull requests
25
Issues
219
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 617 days from 2024-12-01 to 2026-08-09. Pushes: 57 total, peak 5 in a day. Pull requests: 25 total, peak 2 in a day. Issues: 219 total, peak 66 in a day. Comments: 59 total, peak 57 in a day. Stars: 0 total, peak 0 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

  • Issue#708github-actions[bot]2026-05-11 19:55
    [Codacy/Security] TypeNameHandling All is unsafe and can lead to arbitrary code execution in the context of the process.
  • Issue#736github-actions[bot]2026-05-11 01:52
    Investigate Nightly Build Failure
  • Issue#735github-actions[bot]2026-05-10 01:49
    Investigate Nightly Build Failure
  • Issue#725github-actions[bot]2026-04-27 16:35
    [Codacy/Security] TypeNameHandling All is unsafe and can lead to arbitrary code execution in the context of the process.
  • Issue#701StuartFerguson2026-04-25 10:15
    [Security] By not specifying a USER, a program in the container may run as 'root'. This is a security hazard.
  • Issue comment#705codacy-production[bot]2026-04-25 10:04
    Remove unit tests from release, update trace log paths
  • Issue#703github-actions[bot]2026-04-25 00:57
    Investigate Nightly Build Failure
  • Issue#703github-actions[bot]2026-04-25 00:57
    Investigate Nightly Build Failure
  • Issue#699github-actions[bot]2026-04-18 00:58
    Investigate Nightly Build Failure
  • Issue#699github-actions[bot]2026-04-18 00:58
    Investigate Nightly Build Failure
  • Pull request#682StuartFerguson2026-02-27 13:29
  • Releasegithub-actions[bot]2026-02-26 16:25
    2026.2.2
  • Pull request#679StuartFerguson2026-02-26 15:36
  • Issue#676StuartFerguson2026-02-26 10:33
    Investigate Nightly Build Failure
  • Issue#675StuartFerguson2026-02-26 10:33
    Investigate Nightly Build Failure
  • Issue#675github-actions[bot]2026-02-14 00:43
    Investigate Nightly Build Failure
  • Issue#675github-actions[bot]2026-02-14 00:43
    Investigate Nightly Build Failure
  • Pull request#671StuartFerguson2026-01-01 11:26
  • Pull request#671StuartFerguson2026-01-01 10:32
  • Issue#641StuartFerguson2025-12-29 09:52
    Investigate Nightly Build Failure
  • Issue#640StuartFerguson2025-12-29 09:52
    Investigate Nightly Build Failure
  • Issue#640StuartFerguson2025-12-29 09:51
    Investigate Nightly Build Failure
  • Issue#641StuartFerguson2025-12-29 09:51
    Investigate Nightly Build Failure
  • Issue#641StuartFerguson2025-12-29 09:51
    Investigate Nightly Build Failure
  • Issue#640StuartFerguson2025-12-29 09:51
    Investigate Nightly Build Failure

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