openai/codex · error · anyhow::Error
timed out after {}ms connecting runner {pipe_label}
Error message
timed out after {}ms connecting runner {pipe_label} What it means
Error "timed out after {}ms connecting runner {pipe_label}" thrown in openai/codex.
Source
Thrown at codex-rs/windows-sandbox-rs/src/elevated/runner_client.rs:277
)? {
result
} else {
let cancel_ok = unsafe { CancelSynchronousIo(thread_handle) };
if cancel_ok == 0 {
let err = unsafe { GetLastError() };
if err != ERROR_NOT_FOUND {
Err(anyhow::anyhow!(
"CancelSynchronousIo failed for runner {pipe_label} connect thread: {err}"
))
} else if let Some(result) = try_take_completed_connect_result(
&mut connect_thread,
&connect_result_rx,
thread_handle,
&pipe_label,
)? {
result
} else {
Err(anyhow::anyhow!(
"timed out after {}ms connecting runner {pipe_label}",
RUNNER_PIPE_CONNECT_TIMEOUT.as_millis()
))
}
} else {
// Do not join the helper thread on the timeout path. Parent-side cleanup will
// close the pipe handles, which lets the blocked connect unwind without
// risking another indefinite wait here.
Err(anyhow::anyhow!(
"timed out after {}ms connecting runner {pipe_label}",
RUNNER_PIPE_CONNECT_TIMEOUT.as_millis()
))
}
}
}
Err(mpsc::RecvTimeoutError::Disconnected) => {
if let Some(connect_thread) = connect_thread.take() {
let _ = connect_thread.join();View on GitHub (pinned to 339751715c)
When it happens
Trigger: Thrown at codex-rs/windows-sandbox-rs/src/elevated/runner_client.rs:277 when the library encounters an invalid state.
Common situations: See trigger scenarios.
Understand the failure class
- Timeouts: ETIMEDOUT, deadlines, and hung requests — what actually expires when a request times out.
AI-assisted analysis of openai/codex@339751715c (2026-08-25).
Data as JSON: /api/errors/2fd085cc600cb77b.
Report an issue: GitHub.