TiUP don't respect pipeline rules
Open
Nobody has claimed this yet.
type/bug
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Bug Report
-
What did you do?
tiup .... | tee my.log
(in ascreen, but this is not important) -
What did you expect to see?
Regular output.
Since tiup is in a pipe, it should not use too much ctrl-chars. -
What did you see instead?
Crazily binding output with unrecognizable chars -
What version of TiUP are you using (
tiup --version)?
v1.3.2 tiup
Go Version: go1.13
Git Branch: release-1.3
GitHash: 2d88460
Contributor guide
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 source file or test is identified in the report. Start by reproducing tiup .... | tee my.log with TiUP v1.3.2 and compare piped output with regular output. Done means piped output remains readable and does not emit excessive control characters.
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
- 35/100