Solution skill
DeepInfra sandbox gotchas: stopped-sandbox exec and failed creates
Complete solution
DeepInfra sandbox gotchas: stopped-sandbox exec and failed creates. exec on a stopped sandbox raises ConflictError (409): restart the sandbox before running commands. Use when hitting this exact issue with DeepInfra sandbox gotchas. Not for unrelated errors or different features.
TL;DR
Exec on a stopped sandbox raises ConflictError (409): restart the sandbox before running commands. If Sandbox.create fails while the sandbox is coming up, the raised error carries the sandboxId: use it to inspect or terminate the orphaned sandbox instead of leaking capacity. Use try/finally or a context manager so sandboxes terminate even when the workload throws; a leaked sandbox keeps counting against the per-account cap until you clean it up.
The error
stopped-sandbox exec and failed createsFix
Exec on a stopped sandbox raises ConflictError (409): restart the sandbox before running commands. Expected: You get the expected result; the problem is gone.
If Sandbox.create fails while the sandbox is coming up, the raised error carries the sandboxId: use it to inspect or terminate the orphaned sandbox instead of leaking capacity. Expected: You get the expected result; the problem is gone.
Re-run the original operation and confirm the error is gone. Expected: no error, normal output.
When to use
- You hit this exact error with DeepInfra sandbox gotchas.
- The symptom matches: stopped-sandbox exec and failed creates.
When NOT to use
- A different error message from DeepInfra sandbox gotchas; the cause here is specific to this error.
- Unrelated DeepInfra sandbox gotchas issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.
Compatibility
Reported against DeepInfra sandbox gotchas.
Variant phrasings
stopped-sandbox exec and failed creates
Why it happens
Two sandbox failure modes with built-in recovery handles.
Edge cases
- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.
Evidence
Source: Two sandbox failure modes with built-in recovery handles.
Verified resolution: [deepinfra-node README]: exec on a stopped sandbox raises ConflictError (409): restart the sandbox before running commands. If Sandbox.create fails while the sandbox is coming up, the raised error carries the sandboxId: use it to inspect or terminate the orphaned sandbox instead of leaking capacity. Use try/finally or a context manager so sandboxes terminate even when the workload throws; a leaked sandbox keeps counting against the per-account cap until you clean it up.
Source URL: https://github.com/deepinfra/deepinfra-node/blob/HEAD/README.MD
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_6x5QF8ZO4_kICroT9KBfFg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">DeepInfra sandbox gotchas: stopped-sandbox exec and failed creates <span>— Vectle</span></a>