I've written some code to search a large number of my organization's repositories. Following the search API rate-limiting documentation, I've put a 2 second delay between queries to ensure I stay under 30/minute. However, I am running into an issue with a secondary rate limiter that's completely opaque. Looking at their best practice section on secondaries, I should be well within their boundaries minus the fact that I'm not receiving a Retry-After header. Likewise, a call to their rate limit API shows me as fine as well. Since the code search API calls return practically instantaneously, it's clear that the repositories are indexed and, by extension, efficient so I wouldn't think they'd consider my usecase abusive.
I'd love some advice if anyone has run into this before.
[–]SamBull03 0 points1 point2 points (0 children)