coreweave/cwsandbox-client v0.22.0

v0.22.0

Repository: coreweave/cwsandbox-client

Tag: v0.22.0

Published: 2026-04-29T14:50:35Z

Prerelease: no

Release notes:

v0.22.0 (2026-04-29)

_This release is published under the Apache-2.0 License._

Features

• Add poll retry budget and RPC timeout configuration (`db6c818`)

Plumbing for the upcoming retry wrapper. Two SandboxDefaults fields:

• poll_retry_budget_seconds (30s): wall-clock retry budget. Separate

from request_timeout_seconds because one is cumulative across attempts, the other is per-call.

• poll_rpc_timeout_seconds (15s): per-call poll Get deadline so a

wedged poll fails fast instead of riding the broader request timeout.

_validate_poll_config rejects NaN/inf/negative at every construction site; NaN would silently defeat the wall-clock deadline check once the retry loop lands.

• Add retryable/fatal exception subclasses for poll translation (`720db5f`)

SandboxNotRunningError and SandboxTimeoutError each span retryable and fatal cases (UNAVAILABLE vs CANCELLED; DEADLINE_EXCEEDED vs command timeout). Class-based dispatch can't distinguish them today, blocking the upcoming poll retry classifier.

Add four subclasses and wire the translator to emit them: SandboxUnavailableError, SandboxRequestTimeoutError, SandboxCommandTimeoutError, SandboxResourceExhaustedError. Umbrella parents are preserved so existing except clauses still catch.

• Retry post-stop NOT_FOUND before surfacing backend ambiguity (`1adca9b`)

The backend persists terminal state for stopped sandboxes, so post-stop Get should return COMPLETED or FAILED. NOT_FOUND here is a narrow race with the backend's terminal-state write, or rollout skew.

On post-stop NOT_FOUND (_stop_owned or _missing_ok_observe path), retry Get within NOT_FOUND_AFTER_STOP_RETRY_BUDGET_SECONDS (2s). If the race resolves, waiters see the real terminal. If NOT_FOUND persists, raise SandboxTerminalStateUnavailableError so callers see the ambiguity explicitly rather than a fabricated terminal.

The retry lives in _do_poll_complete, not _classify_poll_error, because NOT_FOUND retryability is contextual (stop-state-machine-aware), not class-based. External-delete NOT_FOUND still surfaces immediately.

• Retry transient errors in the sandbox-status poll loop (`50dcbb9`)

A single UNAVAILABLE/DEADLINE_EXCEEDED blip or RESOURCE_EXHAUSTED spike previously propagated as a fatal SandboxError even when the sandbox itself was healthy. Wrap the shared _running_task / _complete_task with _poll_with_retry; _classify_poll_error dispatches on subclass, with SandboxNotFoundError short-circuiting to fatal.

Retry state lives in the coroutine, not on self, because concurrent waiters share the poll task.

Honors AIP-193 retry_delay when present (capped so a misconfigured server can't stall). Decorrelated jitter on the no-hint path prevents fleet-wide synchronization during regional outages.

---

Detailed Changes: v0.21.0...v0.22.0