Skip to content

quality-of-service exceeds API rate limit during issue search #589

@yegor256

Description

@yegor256

I see this here:

👉 Running quality-of-service (#2) at judges/quality-of-service/ (2m44s already)...
GET https://api.github.com/search/issues?per_page=100&q=repo%3Aobjectionary%2Feolang-paper+type%3Aissue+created%3A2024-12-26..2025-01-25 -> 403 / API rate limit exceeded for user ID 9535539. If you reach out to GitHub Support for help, please include the request ID 1C45:12F767:6C7E73:D8C627:6814705C and timestamp 2025-05-02 07:12:28 UTC.
GET https://api.github.com/search/issues?per_page=100&q=repo%3Aobjectionary%2Feolang-paper+type%3Aissue+created%3A2024-12-26..2025-01-25 -> 403 / API rate limit exceeded for user ID 9535539. If you reach out to GitHub Support for help, please include the request ID 1C40:33FC8D:C99273:1931EF1:68147060 and timestamp 2025-05-02 07:12:32 UTC.
GET https://api.github.com/search/issues?per_page=100&q=repo%3Aobjectionary%2Feolang-paper+type%3Aissue+created%3A2024-12-26..2025-01-25 -> 403 / API rate limit exceeded for user ID 9535539. If you reach out to GitHub Support for help, please include the request ID 1C40:33FC8D:C9AE97:1935787:68147068 and timestamp 2025-05-02 07:12:40 UTC.
GET https://api.github.com/search/issues?per_page=100&q=repo%3Aobjectionary%2Feolang-paper+type%3Aissue+created%3A2024-12-26..2025-01-25 -> 403 / API rate limit exceeded for user ID 9535539. If you reach out to GitHub Support for help, please include the request ID 1C40:33FC8D:C9E629:193C733:68147079 and timestamp 2025-05-02 07:12:57 UTC.

I don't understand why this happens. We should be "quota-aware" and such situations must be avoided.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinggood-titlehelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions