tt connect insists on tt.yaml
Open
Nobody has claimed this yet.
feature
- Dominant language
- Go
- Stars
- 113
- Forks
- 18
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 23
Description
$ tt connect var/run/router-001/tarantool.control
⨯ tt.yaml not found
@oleg-jukovec points me that I should use ./var/run/router-001/tarantool.control.
However, if the file exists, it is quite natural to assume that I want to connect to an instance using the file.
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 tracing the tt connect command and how it handles the supplied var/run/router-001/tarantool.control path. Confirm that an existing control file can be treated as the connection target without requiring tt.yaml; done means the shown command connects successfully when that file exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100