Issue Pool Improvements #41
Merged
sachin-panayil merged 2 commits intomainfrom Jul 7, 2025
Merged
Conversation
Signed-off-by: Sachin Panayil <sachinpanayil01@gmail.com>
Signed-off-by: Sachin Panayil <sachinpanayil01@gmail.com>
decause-gov
approved these changes
Jul 7, 2025
| // process repositories in chunks of 3 for parallel processing | ||
| for (let i = 0; i < repoInfo.length; i += CONFIG.concurrentRepos) { | ||
| const chunk = repoInfo.slice(i, i + CONFIG.concurrentRepos) | ||
| console.log(`Processing chunk ${Math.floor(i/CONFIG.concurrentRepos) + 1}/${Math.ceil(repoInfo.length/CONFIG.concurrentRepos)} (${chunk.length} repos)`) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue Pool Improvements
Problem
Previously, the data parsing was shaky and we were not handling rate limiting. This would cause alot of 403 and 429 errors.
Solution
The changes take this into account by adding simple rate limiting and add parallel processing to speed up the script time.
Result
We should be able to hit all repos in codegov.json without recieving any rate limiting errors.
Notes
Test Plan
Ran the script using
node ../config/updateIssuePool.js