Better indication that host are really dont answer / not exists / etc / instead of 0ms with empty chart [windows]
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 12.7k
- Forks
- 366
- Avg merge
- 7d 7h
- Merged PRs (30d)
- 1
Description
Maybe its windows-only?
as in the title
how one can say whats going on - the app shows 0ns dots and nothing, while windows's ping different replies why the host cant be reach. It will he helpful to see those replies or something like that without need to run regular ping before gping
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
The issue names no source file, test, or entry point. Start by reproducing the empty 0ns chart on Windows and compare it with the operating system's ping responses. Done means unreachable or non-existent hosts are visibly distinguished from successful zero-latency results without requiring a separate ping command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100