Skip to content

fix(sdk): honor sandbox readiness deadlines - #449

Open
Maya-Kid wants to merge 1 commit into
deeplethe:devfrom
Maya-Kid:fix/sdk-readiness-deadline
Open

Maya-Kid wants to merge 1 commit into
deeplethe:devfrom
Maya-Kid:fix/sdk-readiness-deadline

Conversation

@Maya-Kid

Copy link
Copy Markdown

A sandbox could be reported ready after the configured readiness timeout if its status request returned late. Python, TypeScript, and MCP now cap status requests and polling delays by the remaining monotonic budget and reject late ready responses. MCP shares one deadline across the batch.

On readiness failure, the create helpers attempt to delete only the sandboxes created by that call. Waiting on an existing sandbox leaves it in place. Status errors from the control plane still propagate. Python and MCP use HTTP transport timeouts, so an active response stream may finish after the deadline and is checked before its readiness result is accepted.

Regression tests cover late readiness, remaining request budgets, cleanup ownership, and explicit status errors. Validation passed on Python 3.9 and 3.12 (41 tests each), TypeScript (53 tests, build and lint), and both MCP CI dependency sets (43 tests each).

Signed-off-by: dada-yan <BinjunYann@gmail.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant