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
Describe the bug
We were using 1.0.132 before, starting using 1.0.143 since Friday. Our process iterates across 5 Git organizations and creates PRs in each if it finds a match. It was running fine in 1.0.132, but fails in 1.0.143 after iterating through 1 or 2 Git orgs with the rate limit exception.
Exception in thread "main" org.kohsuke.github.GHException: Failed to retrieve https://api.github.com/search/code?q=filename%3ADockerfile+user%3Acbsi-cmg+FROM+xyz+container+pipeline+docker.jfrog.io%2Frv-python-3+8-buster
at org.kohsuke.github.GitHubPageIterator.fetch(GitHubPageIterator.java:155)
at org.kohsuke.github.GitHubPageIterator.hasNext(GitHubPageIterator.java:91)
at org.kohsuke.github.PagedSearchIterable$1.hasNext(PagedSearchIterable.java:86)
at org.kohsuke.github.PagedIterator.fetch(PagedIterator.java:106)
at org.kohsuke.github.PagedIterator.hasNext(PagedIterator.java:74)
at org.kohsuke.github.PagedSearchIterable.populate(PagedSearchIterable.java:65)
at org.kohsuke.github.PagedSearchIterable.getTotalCount(PagedSearchIterable.java:49)
at com.salesforce.dockerfileimageupdate.utils.DockerfileGitHubUtil.findFilesWithImage(DockerfileGitHubUtil.java:88)
at com.salesforce.dockerfileimageupdate.utils.DockerfileGitHubUtil.getGHContents(DockerfileGitHubUtil.java:312)
at com.salesforce.dockerfileimageupdate.subcommands.impl.Parent.execute(Parent.java:61)
at com.salesforce.dockerfileimageupdate.CommandLine.main(CommandLine.java:52)
Caused by: org.kohsuke.github.HttpException: {
"documentation_url": "https://docs.github.com/en/free-pro-team@latest/rest/overview/resources-in-the-rest-api#abuse-rate-limits",
"message": "You have triggered an abuse detection mechanism. Please wait a few minutes before you try again."
}
Can you please look into what changed that we are reaching rate limits so soon?
Thanks,
Keerti
The text was updated successfully, but these errors were encountered:
Describe the bug
We were using 1.0.132 before, starting using 1.0.143 since Friday. Our process iterates across 5 Git organizations and creates PRs in each if it finds a match. It was running fine in 1.0.132, but fails in 1.0.143 after iterating through 1 or 2 Git orgs with the rate limit exception.
Can you please look into what changed that we are reaching rate limits so soon?
Thanks,
Keerti
The text was updated successfully, but these errors were encountered: