Skip to content

feat: custom shutdown timeout - #66

Merged
aidanhibbard merged 1 commit into
mainfrom
feat/shutdown-timeout
Jul 19, 2026
Merged

feat: custom shutdown timeout#66
aidanhibbard merged 1 commit into
mainfrom
feat/shutdown-timeout

Conversation

@aidanhibbard

Copy link
Copy Markdown
Owner

Summary

Adds the ability to configure a custom timeout for shutdown.

Changes

  • Adds timeoutMs to module options.

How to Test

  1. Add the new config key to project
  2. Kill the instance
  3. Confirm shutdown

Screenshots (optional)

N/A

Linked Issues

Closes #62

Checklist

  • I read CONTRIBUTING.md and agree to the Code of Conduct
  • I tested these changes locally
  • Added/updated tests if needed
  • Updated docs (README/docs) if needed
  • npm run ci passes (or npm run lint and npm test at minimum)
  • No breaking changes, or I documented them above

@aidanhibbard aidanhibbard self-assigned this Jul 19, 2026
@aidanhibbard aidanhibbard added the enhancement New feature or request label Jul 19, 2026
@coderabbitai

coderabbitai Bot commented Jul 19, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 41 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

Run ID: 2254bbcf-a552-4afc-a26d-1d3a6fc1e465

📥 Commits

Reviewing files that changed from the base of the PR and between 5cba104 and e55a3cc.

📒 Files selected for processing (2)
  • docs/api.md
  • src/module.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/shutdown-timeout

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.

@aidanhibbard
aidanhibbard merged commit e9c2546 into main Jul 19, 2026
3 checks passed
@aidanhibbard
aidanhibbard deleted the feat/shutdown-timeout branch July 19, 2026 22:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Expose processor.shutdown.timeoutMs in module options

1 participant