shell-pool / shell-pool/shpool
shpool attach returns immediately with status code 1 and no output
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2k
- Forks
- 67
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 15
Description
AI Policy Ack
Ack.
What happened
After using shpool for a while, with a specific session, it suddenly stopped working. shpool attach -f XYZ started exiting immediately with no output, status code 1.
Using SHPOOL_LOG=debug didn't help (still no output).
Only after I did a killall shpool did it work again.
What I expected to happen
It should work.
To Reproduce
I have no idea how it got into this state.
Version info
shpool 0.9.3 (cl/884794100)
Logs
shpool log tail.txt
That's the end of the log file, from after it broke. I'm reluctant to include more of the log because it contains records of the commands executed in the shell, which are private. But I've saved the full log, for now, so if you want me to look for something specific within it, I can.
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 attached shpool.log.tail.txt and the reported shpool attach -f XYZ command; compare its status-1, no-output behavior with a working attach after killall shpool. The issue names no source file, test, or reliable reproduction, so done means identifying the stale state causing the failure and restoring normal attach behavior.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100