`tt stop` kills non-watchdog process, which PID is in .pid file
Open
Nobody has claimed this yet.
3sp
bug
teamE
- Dominant language
- Go
- Stars
- 113
- Forks
- 18
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 23
Description
Sometimes, when tt watchdog process is dead, and "its" PID may be taken by other process. .pid file still exists. And tt stop will try to kill this process. Need a mechanism to check if the process if a real tt watchdog.
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 tt stop entry point and trace how the .pid file is read and the process is terminated. Determine how to verify that the PID belongs to the tt watchdog, then add coverage for a stale PID file whose PID has been reused; done means tt stop does not kill the unrelated process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100