bug: doesnt check if pid is already running
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 1.1k
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
ran into a weird bug today where one of my .pid files in monu was 415, but I had another process running as pid 415 and monu couldn't kill it (it would give me a EPERM error and crash the app if I tried to kill/restart).
Killing process 415 (it was some other app I was running) fixed the issue. So to fix this I guess we should check on startup if the pid exists already?
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
No file or test is named. Trace monu's startup and process kill/restart path, then reproduce the case where a .pid file points to another running process; done means startup or restart no longer targets the unrelated process or crashes on EPERM.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100