sandbox get reports Phase: Error with no reason; forward/stop/start error messages don't point back to root cause
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 8.7k
- Forks
- 1.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 253
Description
Summary
When a sandbox is in Phase: Error, openshell sandbox get <name> shows the phase but no explanation of what happened. Dependent commands also return generic, disconnected errors:
openshell forward start --background <port> <name>→sandbox is not ready(no mention of Error phase or its cause)openshell sandbox stop <name>→sandbox must be Ready to stop (current phase: Error)
A user has to separately run openshell logs <name> and manually correlate timestamps to find the actual failure (in our case, a supervisor session stream error coinciding with an SSH disconnect).
Expected
sandbox get should include a reason/last-error field when Phase: Error, and dependent commands (forward start, stop) should surface that same reason instead of a generic "not ready"/phase-mismatch message.
openshell version: 0.0.116
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 by locating the implementations of openshell sandbox get, forward start, and sandbox stop, then trace how the sandbox Error phase and its cause are represented. Reproduce the behavior with sandbox commands and inspect the related logs. Done means get and the dependent commands surface the same useful last-error reason instead of disconnected generic messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100