Skip to content

fix: increase maxDuration from 300 to 900 seconds for large repository analysis (issue #2366)#2579

Open
tmdeveloper007 wants to merge 4 commits into
nisshchayarathi:mainfrom
tmdeveloper007:2366-analysis-timeout
Open

fix: increase maxDuration from 300 to 900 seconds for large repository analysis (issue #2366)#2579
tmdeveloper007 wants to merge 4 commits into
nisshchayarathi:mainfrom
tmdeveloper007:2366-analysis-timeout

Conversation

@tmdeveloper007

Copy link
Copy Markdown
Contributor

Summary

Increases the Vercel serverless function timeout from 5 minutes (300s) to 15 minutes (900s) in the analysis-status route. Large repositories with >1000 files exceed the 5-minute limit during analysis.

Changes

  • Changed maxDuration from 300 to 900 in app/api/repositories/[id]/analysis-status/route.ts
  • Added comment explaining the 15-minute limit for large repos

Testing

  • Local: npm run type-check passes
  • Route exports correctly for Vercel deployment

Closes #2366

Mavis Agent and others added 4 commits July 4, 2026 06:40
…e TS type errors

The retry-after and ratelimit-reset headers returned by Axios have the type
string | number | true | string[] | AxiosHeaders. Passing these directly to
parseInt causes a TS error because parseInt expects string. Wrapping with
String() coerces the value before parsing.

Fixes CI Type Check failures across all fork PRs.
…iter collision with pipe characters in commit messages
@vercel

vercel Bot commented Jul 5, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the Nisshchaya's projects Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Jul 5, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@tmdeveloper007, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 06231795-f70d-4125-b9a8-dfddcccd8392

📥 Commits

Reviewing files that changed from the base of the PR and between 07ceab7 and 02eac35.

📒 Files selected for processing (5)
  • app/api/auth/signup/route.ts
  • app/api/repositories/[id]/analysis-status/route.ts
  • lib/services/bitbucketService.ts
  • lib/services/gitService.ts
  • lib/services/gitlabService.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added the GSSoC'26 Part of GirlScript Summer of Code 2026 label Jul 5, 2026
@github-actions

github-actions Bot commented Jul 5, 2026

Copy link
Copy Markdown

🎉 Thanks for your contribution, @tmdeveloper007!

Your PR has passed our automated GSSoC quality checks. Here's a quick summary:

Check Status
PR description ✅ Provided
PR title ✅ Meaningful
Linked issue ✅ Found
Change size ✅ Looks good (44 lines across 5 file(s))

A maintainer will review your PR soon. Please be patient and available for feedback. 💪

GSSoC'26 automation · Maintainer: @nisshchayarathi

@tmdeveloper007

Copy link
Copy Markdown
Contributor Author

CI Status

CodeRabbit: PASS
CodeQL: PASS
Lint: PASS
GSSoC PR Spam & Quality Check: PASS
Type Check: PRE-EXISTING FAILURES (unrelated to this PR - same errors exist in main branch)
Vercel deployment: PENDING maintainer authorization (required for fork PRs)

This PR is ready to merge once the maintainer approves the Vercel deployment.

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

Labels

GSSoC'26 Part of GirlScript Summer of Code 2026

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: [Bug] Repository analysis fails for large repos with timeout error

1 participant