Allow provisioned executors more time to come online (#48575)

mirror of https://github.com/openai/codex.git synced 2026-10-20 17:38:45 +00:00

## Why

A provisioned executor can still be resuming after readiness is reported. Initial connection attempts can exhaust the ordinary registry retry limits before the executor comes online.

## What changed

Retry `environment_offline` registry responses during initial Noise rendezvous connections for provisioned environments until a fixed five-minute deadline, starting after provisioning succeeds. Keep the existing retry limits for other registry errors and stop on permanent failures.

## Testing

Add tests covering the five-minute deadline, ordinary limits for other errors and stalled requests, and termination on a later permanent error. Verify that readiness and info requests remain pending through an extended offline period and succeed using the same environment handle once the executor comes online.

GitOrigin-RevId: e22211499d9ec2f3590e75224eb39e2e4bf3538d

This commit is contained in:

richardopenai

2026-09-27 00:01:17 +00:00

committed by

copyberry

parent 0f9a731ade

commit 985cf47a4e

4 changed files with 236 additions and 9 deletions

									
										codex-rs/exec-server/src/client.rs
									
		-1
	
												View File
												
				@@ -150,7 +150,6 @@ mod recovery;

				#[path = "client_refresh.rs"]

				mod refresh;

				pub(crate) use connection_failure::can_retry_connection_attempt;

				#[cfg(test)]

				pub(crate) use recovery::is_environment_offline_error;

				pub(crate) use recovery::is_retryable_recovery_error;