You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
we are building a software that aims to find out what repositories contain a specific file (eg: .gitignore)
In order to obtain that file, we send our requests to the bitbucket REST APIs after parsing the list of repositories (https://api.bitbucket.org/2.0/repositories).
The rate-limit is pretty high but we need to ensure that, if something goes wrong and that limits are hit, we can recover our process from last successful request.
We have implemented a simple solution but it’s really hard to test.
We cannot exhaust our resources (60k https r/h and 1k r/h on repos) every time we want to check out if the implemented solution is correct (and it’s really a bad idea to waste server resources only for these tests).
Do you have any ideas on how manage this problem?