Skip to content

Allow provisioned executors more time to come online - #48575

Merged
copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/e22211499d9ec2f3590e75224eb39e2e4bf3538d
Sep 27, 2026
Merged

copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/e22211499d9ec2f3590e75224eb39e2e4bf3538d

Conversation

@copyberry

@copyberry copyberry Bot commented Sep 27, 2026 •

Copy link
Copy Markdown

Allow provisioned executors more time to come online

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.

## 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
@copyberry
copyberry Bot force-pushed the copyberry/codex-internal-to-codex-oss/e22211499d9ec2f3590e75224eb39e2e4bf3538d branch from e620752 to 985cf47 Compare September 27, 2026 00:01
@copyberry
copyberry Bot merged commit 985cf47 into main Sep 27, 2026
@copyberry
copyberry Bot deleted the copyberry/codex-internal-to-codex-oss/e22211499d9ec2f3590e75224eb39e2e4bf3538d branch September 27, 2026 00:01
@github-actions github-actions Bot locked and limited conversation to collaborators Sep 27, 2026
@rafaself
rafaself deployed to issue-triage September 27, 2026 00:04 — with GitHub Actions Active
@rafaself
rafaself deployed to issue-triage September 27, 2026 00:04 — with GitHub Actions Active
@rafaself
rafaself deployed to issue-triage September 27, 2026 00:04 — with GitHub Actions Active
@Tarukaja
Tarukaja deployed to issue-triage September 27, 2026 00:35 — with GitHub Actions Active
@Tarukaja
Tarukaja deployed to issue-triage September 27, 2026 00:35 — with GitHub Actions Active
@Tarukaja
Tarukaja deployed to issue-triage September 27, 2026 00:35 — with GitHub Actions Active
@Tarukaja
Tarukaja deployed to issue-triage September 27, 2026 00:36 — with GitHub Actions Active
@wzgrx
wzgrx deployed to issue-triage September 27, 2026 01:12 — with GitHub Actions Active
@lynnswap
lynnswap deployed to issue-triage September 27, 2026 01:31 — with GitHub Actions Active
@nodchip
nodchip deployed to issue-triage September 27, 2026 01:31 — with GitHub Actions Active
@nodchip
nodchip deployed to issue-triage September 27, 2026 01:31 — with GitHub Actions Active
@nodchip
nodchip deployed to issue-triage September 27, 2026 01:31 — with GitHub Actions Active
@yeongJD
yeongJD deployed to issue-triage September 27, 2026 01:32 — with GitHub Actions Active
@nodchip
nodchip deployed to issue-triage September 27, 2026 01:32 — with GitHub Actions Active
@yeongJD
yeongJD deployed to issue-triage September 27, 2026 01:32 — with GitHub Actions Active
@yeongJD
yeongJD deployed to issue-triage September 27, 2026 01:32 — with GitHub Actions Active
@yeongJD
yeongJD deployed to issue-triage September 27, 2026 01:33 — with GitHub Actions Active
@Bullitata
Bullitata deployed to issue-triage September 27, 2026 01:33 — with GitHub Actions Active
@Bullitata
Bullitata deployed to issue-triage September 27, 2026 01:33 — with GitHub Actions Active
@Bullitata
Bullitata deployed to issue-triage September 27, 2026 01:33 — with GitHub Actions Active
@vicaleca
vicaleca deployed to issue-triage September 27, 2026 01:46 — with GitHub Actions Active
@vicaleca
vicaleca deployed to issue-triage September 27, 2026 01:46 — with GitHub Actions Active
@vicaleca
vicaleca deployed to issue-triage September 27, 2026 01:46 — with GitHub Actions Active

This branch was successfully deployed

1 active deployment
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.