You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experiencing the same problem where the Rails and Rubygems repos have 0 issues, despite them having many open issues in reality:
I think this could also be why my weekly emails have stopped coming in. I have my email frequency set to once a week, tracking only those 2 repos, and the last emails I got were from June 8 with only Rails issues, and June 2nd with both Rails and Rubygems issues. No more emails after those dates.
@rgerhards and @jeromedalbert the issue is with the github api and the pagination used along side to it already raised the PR with the fix. Please attached screenshot for the same.
This is caused (at least in part) by hitting limits of the database as many tables are using "integer" and "serial" instead of "bigint" and "bigserial" (64bit integers).
E, [2026-02-02T15:37:35.582127 #5] ERROR -- : [ActiveJob] [PopulateIssuesJob] [cffcb87a-a234-487b-9bf8-07fefe0c8213] Error performing PopulateIssuesJob (Job ID: cffcb87a-a234-487b-9bf8-07fefe0c8213) from Sidekiq(default) in 550.91ms: ActiveRecord::RangeError (PG::NumericValueOutOfRange: ERROR: integer out of range
):
/app/vendor/bundle/ruby/3.2.0/gems/rack-mini-profiler-3.1.1/lib/patches/db/pg.rb:69:in `exec_params'
/app/vendor/bundle/ruby/3.2.0/gems/rack-mini-profiler-3.1.1/lib/patches/db/pg.rb:69:in `exec_params'
# ...
irb(main):008:0> IssueAssignment.count
D, [2026-02-02T15:50:41.899327 #5] DEBUG -- : IssueAssignment Count (19738.7ms) SELECT COUNT(*) FROM "issue_assignments"
=> 24965798
Fixing in #1844, I'll update other columns shortly.
I just received my weekly CodeTriage email thanks to this fix, so I guess it's time for me to get back to doing more OSS work. 😄 Thank you @schneems for this great project and for your "How To Open Source" book!
Activity
rgerhards commentedon Aug 27, 2025
I also tried to delete and re-create my account, as I saw this is one other issue here on the issue tracker. That did not help.
jeromedalbert commentedon Sep 7, 2025
I am experiencing the same problem where the Rails and Rubygems repos have 0 issues, despite them having many open issues in reality:
I think this could also be why my weekly emails have stopped coming in. I have my email frequency set to once a week, tracking only those 2 repos, and the last emails I got were from June 8 with only Rails issues, and June 2nd with both Rails and Rubygems issues. No more emails after those dates.
Selectus2 commentedon Jan 27, 2026
@rgerhards and @jeromedalbert the issue is with the github api and the pagination used along side to it already raised the PR with the fix. Please attached screenshot for the same.
rgerhards commentedon Jan 27, 2026
@Selectus2 the rsyslog repo still shows 0 - is this likely to change in the next days? Or did I misunderstand?
Selectus2 commentedon Jan 27, 2026
@rgerhards the issue will get resolved once #1843 this get merged
schneems commentedon Feb 2, 2026
This is caused (at least in part) by hitting limits of the database as many tables are using "integer" and "serial" instead of "bigint" and "bigserial" (64bit integers).
Fixing in #1844, I'll update other columns shortly.
schneems commentedon Feb 2, 2026
The other failure is fixed via #1847 due to a failure parsing a missing
last_urllink.https://www.codetriage.com/rsyslog/rsyslog now shows issues
jeromedalbert commentedon Feb 3, 2026
I just received my weekly CodeTriage email thanks to this fix, so I guess it's time for me to get back to doing more OSS work. 😄 Thank you @schneems for this great project and for your "How To Open Source" book!