Skip to content

repo rsyslog/rsyslog always shows 0 issues - re-init possible? #1841

Closed

Description

@rgerhards

Hi,

I noticed that https://github.com/rsyslog/rsyslog always shows 0 issues (see screenshot) albeit there are open ones and properly tagged. See org project board: First Contributions / Onboarding

The same holds true for lib-relp. I tried to solve that ~ 36hrs ago by re-submitting the issues, but that does not help.

Is there anything else I can do to get them integrated into CodeTriage again?

Any help is deeply appreciated!

Image

Activity

  1. rgerhards commented on Aug 27, 2025

    @rgerhards
    Author

    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.

  2. jeromedalbert commented on Sep 7, 2025

    @jeromedalbert

    I am experiencing the same problem where the Rails and Rubygems repos have 0 issues, despite them having many open issues in reality:

    Image

    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.

  3. Selectus2 commented on Jan 27, 2026

    @Selectus2

    @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.

    Image
  4. rgerhards commented on Jan 27, 2026

    @rgerhards
    Author

    @Selectus2 the rsyslog repo still shows 0 - is this likely to change in the next days? Or did I misunderstand?

  5. Selectus2 commented on Jan 27, 2026

    @Selectus2

    @rgerhards the issue will get resolved once #1843 this get merged

  6. schneems commented on Feb 2, 2026

    @schneems
    Member

    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.

  7. schneems commented on Feb 2, 2026

    @schneems
    Member

    The other failure is fixed via #1847 due to a failure parsing a missing last_url link.

    https://www.codetriage.com/rsyslog/rsyslog now shows issues

    Image
  8. jeromedalbert commented on Feb 3, 2026

    @jeromedalbert

    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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions