Clarify tracking of highest and lowest trackable values
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start with the linked pull-request discussion and inspect how the requested limits are stored and written during histogram serialization. Resolve whether configured and actual limits should both be exposed and serialized; the issue does not name a file or test, and its strawman still needs a project decision.
Written by the indexing model from the issue text.
Description
See https://github.com/jonhoo/hdrsample/pull/74#discussion_r158192909 for more context.
We save in fields (and write when serializing) the requested limits, not the actual limits that result from the underlying encoding (which will encompass at least as much as what the user requested, and maybe more). Perhaps we should expose the actual limits of what a particular histogram can do, rather than just regurgitate the limits that the user requested? This would be useful when, say, storing metadata about histograms, since the data actually in the histogram is likely more interesting than the particular subset of values that were initially requested as trackable.
Strawman:
configured_low()for what the user requested when creating the histogramactual_low()for what the histogram can supportconfigured_high(),actual_high()
- Dominant language
- Rust
- Stars
- 373
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from HdrHistogram/HdrHistogram_rust
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
HdrHistogram/HdrHistogram_rust#128 · 5 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 32/100
HdrHistogram/HdrHistogram_rust#127 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
HdrHistogram/HdrHistogram_rust#120 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
HdrHistogram/HdrHistogram_rust#119 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
HdrHistogram/HdrHistogram_rust#114 · 3 comments · 1 reaction ·
All issues in HdrHistogram/HdrHistogram_rust
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
linebender/parley#849 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
boxlite-ai/boxlite#1729 ·
Maintainers usually reply within 1 day
-
external
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
langchain-ai/docs#6255 ·
Maintainers usually reply within 1 day
-
P2 testing
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day