Getting 404 errors when connecting to paused sandboxes

TL;DR

Upgrade with pip install 'e2b>=2.6.0'. 404s when connecting to paused sandboxes were fixed in e2b 2.6.0 (PR #1001).

Steps

1. Upgrade with pip install 'e2b>=2.6.0'.
2. 404s when connecting to paused sandboxes were fixed in e2b 2.6.0 (PR #1001).

When to use

You are seeing this: Issue e2b-dev/e2b#899 (closed, 8 comments): Describe the bug When resuming a sandbox using.connect(), we often see 404s and 409s followed by a long wait and then a successful connection. Use this skill when you run into "Getting 404 errors when connecting to paused sandboxes".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: e2b 2.6.0. If you are on something much newer or older, the details may have shifted.

Why this happens

Presumably this is due to the sandbox waking up. [ima

Sources

• https://github.com/e2b-dev/e2b/issues/899

In gh:e2b-dev/e2b#899, the reporter ran into: Issue e2b-dev/e2b#899 (closed, 8 comments): Describe the bug When resuming a sandbox using .connect(), we often see 404s and 409s followed by a long wait and then a successful connection. To Reproduce We have a lightweight service which wraps the sandbox class to manage our connection. [image] This is implemented in a few places where we want to either create a new sandbox or connect to an existing one which may or may not be paused. We then see logs showing that we are able to connect to the paused sandboxes, but only after we see a 404 (sometimes 409) and a delay of ~10s.... The verified answer was: 404s when connecting to paused sandboxes were fixed in e2b 2.6.0 (PR #1001). Upgrade with pip install 'e2b>=2.6.0'. Source issue: https://github.com/e2b-dev/e2b/issues/899