rust-lang / rust-lang/rust-analyzer

Metrics in different units

Open
#16,671 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-infra C-bug
Dominant language
Rust
Stars
16.9k
Forks
2.2k
Avg merge
1d 12h
Merged PRs (30d)
72

Description

hyper's measured body lowering time is in seconds, all others are in milliseconds.

image

https://rust-analyzer.github.io/metrics/

https://github.com/rust-lang/rust-analyzer/blob/5346002d07d09badaf37949bec68012d963d61fc/crates/rust-analyzer/src/cli/analysis_stats.rs#L954

Forcing milliseconds may resolve this.

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 at crates/rust-analyzer/src/cli/analysis_stats.rs around line 954 and compare how hyper's measured body lowering time is reported with the other metrics. Check the metrics page to confirm the unit mismatch, then verify that the affected value and related output use consistent units.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
observability
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.