Fix Repository Pagination to Prevent Rate Limit Exhaustion#8250
Conversation
|
@iqb430 is attempting to deploy a commit to the jhasourav07's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
This PR effectively resolves the issue of rate limit exhaustion by capping the repository pagination. It aligns with previous decisions made to optimize repository fetching and prevent sequential blocking. Thank you for your contribution! Looking forward to your further input. |
|
🚨 Hey @iqb430, the CI Pipeline is failing on this PR and it has been marked as Please fix the issues before this can be reviewed. Here's how: 1. Run checks locally before pushing: npm run format:check # Check Prettier formatting
npm run lint # Run ESLint
npm run typecheck # TypeScript type check
npm run test # Run unit tests (Vitest)
npm run build # Verify production build passes2. Auto-fix common issues: npm run format # Auto-fix formatting with Prettier
npm run lint -- --fix # Auto-fix lint errors where possible3. Check the full failure log here: Once you push a fix and the CI passes, the |
Aamod007
left a comment
There was a problem hiding this comment.
This PR is currently blocked due to failing CI checks. It looks like removing the repository pagination logic in \lib/github.ts\ caused \lib/github.test.ts\ to fail because the tests expect \guardedFetch\ to be called multiple times for users with more than 100 repositories.
How to fix:
To fix this error, you need to either:
- Restore the pagination logic so that we fetch all repositories (not just the first 100).
- Or, if removing pagination is intentional, update the test cases in \lib/github.test.ts\ (around lines 845-903) to expect only 1 fetch call instead of 3.
I am requesting changes until the CI passes.
Label Justification:
- \level:beginner: 1 file changed.
- \ ype:refactor: Modifies repository fetching logic.
- \mentor:Aamod007: Assigned as required.
Fixes #911.
Changes:
MAX_PAGESlooping infetchReposUncached.