pingcap / pingcap/tiup

TiUP takes a long time to quit

Open
#1,437 2 comments 0 reactions 0 assignees View on GitHub

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

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?

Run tiup cluster --version.

  1. What did you expect to see?

Print:

❯ tiup cluster --version
Starting component `cluster`: /home/yilin/.tiup/components/cluster/v1.5.1/tiup-cluster --version
tiup version 1.5.1 tiup
Go Version: go1.16.5
Git Ref: v1.5.1
GitHash: f00aeb0783f56c0766c39aa765d183a566f8f0d6

And it should quit quickly after printing.

  1. What did you see instead?

It takes a long time to exit.

  1. What version of TiUP are you using (tiup --version)?
1.5.1 tiup
Go Version: go1.16.5
Git Ref: v1.5.1
GitHash: f00aeb0783f56c0766c39aa765d183a566f8f0d6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the delay with tiup cluster --version on TiUP 1.5.1 and compare the observed output and exit time with the expected output in this issue. Trace the CLI entry point and shutdown path to identify what keeps the command running. Done means the version is printed and the command exits promptly.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.