fix(runner): increase tool timeout defaults - #6014
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
Disabled knowledge base sources:
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe runner’s default idle and per-tool-call timeouts increase from 5 minutes to 30 minutes. The TTFB timeout and total run timeout remain unchanged. Self-host documentation and EE/OSS environment examples reflect the new defaults. ChangesRunner timeout defaults
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
Railway Preview Environment
|
Tool calls that produce no intermediate progress currently stop after five minutes. This interrupts legitimate long-running commands and external operations.
This change raises both limits that can stop a quiet tool call:
The 45-minute overall run deadline remains unchanged. Deployments can still override every limit through the existing environment variables. The Docker Compose examples and self-hosting reference now show the new defaults.
Validation
pnpm test: 125 test files and 2,133 tests passed.pnpm run typecheck: passed.git diff --check: passed.How to review
services/runner/src/engines/sandbox_agent/run-limits.tsfor the runtime defaults.