"Max" appears to be unrelated to the actual graph
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 12.7k
- Forks
- 366
- Avg merge
- 7d 7h
- Merged PRs (30d)
- 1
Description
According to this the "max" is 37ms, but looking at the graph we can clearly see several spikes up into 50ms range. The demo gif in the README.md has this same problem.
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 comparing the displayed “max” value with the spikes in the graph shown in the issue and the demo GIF in README.md. Trace where the graph and maximum are calculated, then verify that the reported maximum matches the plotted data. Done means the displayed maximum reflects the highest visible latency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100