`tt start -i` leads to the impossibility of the `tt clean`
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 113
- Forks
- 18
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 23
Description
- Start an instance using
tt start -i. Logs directory is not created. As I see, it is done intentionally here: https://github.com/tarantool/tt/blob/2eba9ef410914341838e744e81c97a8272048a61/cli/running/running.go#L754 - Stop the instance.
- Try to clean files with
tt clean -fand got error:... var/log/instance1: no such file or directory, ascleanassumes that all directories exist when collects files to clean.
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
Read cli/running/running.go around line 754, then trace the cleanup path invoked by tt clean -f. Reproduce the sequence with an instance started using -i and stopped afterward; done means cleanup completes without failing when the logs directory is absent.
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