oxidecomputer / oxidecomputer/sush
Error message when trying to attach to a non-interactive job is misleading.
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3
- Forks
- 0
- Avg merge
- 9d 12h
- Merged PRs (30d)
- 11
Description
I started a regular job, then disconnected from it (not an interactive job)
I can see my job is still running:
lan@castle:~$ /staff/alex/sush job status book-dial-lawn-shock-insect-loop-picnic-filter
✅ Job ID: book-dial-lawn-shock-insect-loop-picnic-filter
913-0000023:2F8JEXDK Started at 2026-09-03 15:58:14.523153172 UTC
However, if I try to attach to it, it claims the job ID is not found:
alan@castle:~$ /staff/alex/sush job attach book-dial-lawn-shock-insect-loop-picnic-filter
❌ Job `book-dial-lawn-shock-insect-loop-picnic-filter` not found
The error should tell me that it's not an interactive job.
Contributor guide
No contributing guide indexed for this repository
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 at the CLI entry point for job attach and trace how a regular, non-interactive job is handled. Update the misleading not-found response to identify that the job is not interactive, then verify the message by attaching to a running regular job.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100