pingcap / pingcap/tiup

replace the port conflict check tool ss with insight

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

Nobody has claimed this yet.

type/feature-request
Dominant language
Go
Stars
466
Forks
338
Avg merge
3d 7h
Merged PRs (30d)
8

Description

Feature Request

Is your feature request related to a problem? Please describe:

Describe the feature you'd like:

ss is the package of iproute2, in some host, this tool maybe not exists. I prefer to implemenet ss -ntl with insight instead.

Why the featue is needed:

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

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 locating the port-conflict check in the tiup repository and reviewing how it invokes ss -ntl. Then inspect the linked insight collector to determine the available replacement entry point. Done means the check works on hosts where iproute2 and ss are unavailable, with equivalent port-conflict detection.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.