Repository navigation
fix(codex): raise thread handshake timeout - #846
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis PR adds a dedicated ChangesThread Handshake Timeout Update
Estimated code review effort: 1 (Trivial) | ~5 minutes Sequence Diagram(s)sequenceDiagram
participant Client
participant CodexAppServer
participant CodexProcess
Client->>CodexAppServer: start()
CodexAppServer->>CodexProcess: initialize
CodexProcess-->>CodexAppServer: initialized
alt resumeThreadId provided
CodexAppServer->>CodexProcess: thread/resume (timeout=THREAD_HANDSHAKE_TIMEOUT_MS)
else new thread
CodexAppServer->>CodexProcess: thread/start (timeout=THREAD_HANDSHAKE_TIMEOUT_MS)
end
CodexProcess-->>CodexAppServer: thread ready
Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint install failed. For unrecoverable errors, disable the tool in CodeRabbit configuration. 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 |
What
Raise the Codex app-server thread handshake budget from 15 seconds to 30 seconds.
Why
Recent Codex builds can take longer than 15 seconds to start or resume a thread after the app-server initializes. Mcode reported
Timed out waiting for thread/start (15000ms)before the provider could complete startup.Key Changes
THREAD_HANDSHAKE_TIMEOUT_MSconstant for Codex thread start and resume.thread/startandthread/resumeuse the 30 second budget and no longer use 15 seconds.Need help on this PR? Tag
/codesmithwith what you need. Autofix is disabled.Summary by CodeRabbit