[
https://issues.apache.org/jira/browse/SLING-13347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18123788#comment-18123788
]
Joerg Hoh commented on SLING-13347:
-----------------------------------
According to the github documentation the rate-limit is 60 requests per hour
for un-authenticated usage, which can easily cause problems. We should think
about using an authenticated usecase,as the limit there is 5'000 requests per
hour.
https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2026-03-10
> Committer CLI: improve handling of github ratelimiting
> ------------------------------------------------------
>
> Key: SLING-13347
> URL: https://issues.apache.org/jira/browse/SLING-13347
> Project: Sling
> Issue Type: Task
> Components: Committer CLI
> Reporter: Joerg Hoh
> Assignee: Roy Teeuwen
> Priority: Major
>
> When using the Committer CLI today, I receive this with the "verify" command:
> {noformat}
> CI Status: INVALID:
> Failed to get CI Status: java.lang.NullPointerException: Cannot invoke
> "com.google.gson.JsonElement.getAsString()" because the return value of
> "com.google.gson.JsonObject.get(String)" is null
> CI Status Url:
> https://api.github.com/repos/apache/sling-org-apache-sling-xss/commits/org.apache.sling.xss-2.4.12/status
> CI Status Body: {"message":"API rate limit exceeded for 193.105.139.131. (But
> here's the good news: Authenticated requests get a higher rate limit. Check
> out the documentation for more
> details.)","documentation_url":"https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting"}
> {noformat}
> We might want to improve the code a bit to handle the rate limiting;
> depending on the number of artifacts to verify it could also make sense that
> the CLI throttles itself a bit, so it won't run into the GH ratelimiting.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
