Idea: `tt start` should check instance start status
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 113
- Forks
- 18
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 23
Description
tt start should include a sanity check to ensure that the Tarantool instances are starting correctly. Sometimes, an instance may exit with an error for some reason, but tt start does not report this, so tt start now effectively consists of two commands: tt start + tt status. tt status should be used to check whether all instances have started. tt start could wait for a short period of time to check if the instances are still running and, if not, it could print the exit code and the last log lines, for example.
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 by running tt start on an instance that exits with an error, then inspect how tt start and tt status report instance state. Define a short wait and the expected failure output from the issue, including the exit code and recent log lines. Done means tt start detects failed instances instead of requiring a separate tt status command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100