max-mapper / max-mapper/HyperOS
Problem: `linux status` throws error if not booted once
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 124
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Steps to reproduce:
npm install linux -g
linux init
linux status
Then I get this error:
/usr/local/lib/node_modules/linux/cli.js:232
if (err) throw err
^
Error: ENOENT: no such file or directory, open '/Users/johndoe/some_project/linux/linux.pid'
Once I actually boot the VM for the first time it's fine:
$ sudo linux boot
Linux has booted { ip: '192.168.64.137',
hostname: 'joe-pony-man-bearpig',
pid: 1337 }
$ linux status
Linux is running { pid: 1337 }
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
Reproduce the reported sequence with npm install linux -g, linux init, and linux status, then inspect cli.js around line 232 and the handling of linux.pid. Confirm the behavior after the first boot as well. Done means linux status handles an initialized but never-booted VM without throwing an ENOENT error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100