Skip to content

fix: resolve timeout and rate limiting in github repo fetching (#153) - #543

Open
Rajen5145 wants to merge 2 commits into
SamXop123:mainfrom
Rajen5145:fix/repo-fetch-timeout-153
Open

fix: resolve timeout and rate limiting in github repo fetching (#153)#543
Rajen5145 wants to merge 2 commits into
SamXop123:mainfrom
Rajen5145:fix/repo-fetch-timeout-153

Conversation

@Rajen5145

Copy link
Copy Markdown

Description

Summary of Changes

  • Error Handling & Architecture Alignment: Refactored fetchUserRepos to use the project's internal httpRequest utility and assertOk validation, preserving proper mapping for GitHub error statuses (NOT_FOUND, RATE_LIMIT, API_DOWN, and API_ERROR).
  • Optimized Asynchronous Flow: Streamlined data resolution in getGitHubUserData to execute network requests concurrently via Promise.all, preventing unnecessary serial bottlenecks and reducing overall API latency.
  • Pagination Integrity: Maintained complete multi-page repository fetching support up to the final page while eliminating unhandled infinite-loop failure points that trigger serverless execution timeouts.
  • Testing & Verification: Ran full test suites locally via npm test—all 19 test suites and 322 unit tests passed with zero regressions.

Closes #153

@vercel

vercel Bot commented Aug 23, 2026

Copy link
Copy Markdown

@Rajen5145 is attempting to deploy a commit to the Dot_NotSam's projects Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: Performance timeout and rate limiting for profiles with high repository counts

1 participant