process was not killed when auto paused
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13.9k
- Forks
- 1k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 70
Description
Describe the bug
The sandbox was created by beta_create with auto_paused=True, and there's a process of Next.js server running at port 3000, after auto pausing and resuming the sandbox, the port of 3000 is still in use but I cannot find any command through sandbox.commands.list
To Reproduce
Steps to reproduce the behavior:
from e2b import Sandbox
sbx = Sandbox.beta_create(auto_paused=True, timeout=3599)
# start a next.js server here
# after timeout, re-connect to that sandbox
sbx = Sandbox.connect(sandbox_id="")
sbx.commands.list() # only get a blank list, but the port 3000 is still in use
Expected behavior
Option 1: All processes should be killed properly when auto paused
Option 2: All processes should be resumed auto paused, and they could be list by sandbox.commands.list
Additional context
Sandbox ID: ikyarydnag80kc0o8tq8se2b
Team ID: 0be2861d-c33f-4970-ae30-57e21a4c9a3d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Python reproduction using Sandbox.beta_create, Sandbox.connect, and sandbox.commands.list, with a Next.js server listening on port 3000. Trace what happens to the process across auto-pause and resume. Done means the chosen behavior is consistent: the process is either killed and the port released, or resumed and visible through sandbox.commands.list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, python
- Domain
- devtools, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100