fix: pass missing parameter in MaxSampleMetricContexts#916
Open
KowalskiThomas wants to merge 2 commits intomasterfrom
Open
fix: pass missing parameter in MaxSampleMetricContexts#916KowalskiThomas wants to merge 2 commits intomasterfrom
MaxSampleMetricContexts#916KowalskiThomas wants to merge 2 commits intomasterfrom
Conversation
MaxSampleMetricContexts
f5106c8 to
314ba32
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
When creating a new metric context, the
rateparameter is currently not passed to the metric constructor. I believe that means sampling rates for histogram/distribution/timing metrics are ignored. It also means that the parameters we did pass to the constructor were shifted by one position, making them do not what we wanted.Description of the Change
This adds forwarding of the
rateparameter to the constructor we call, and adds a unit test to ensure forwarding is done properly.Possible Drawbacks
I don't see any.
Reproducer
This is as simple as I could make it -- if we pass parameters properly, the "max samples per context" limiting should work.
Additional Notes
❓ I think this problem is one that would typically be detected and prevented by even basic static typing / static correctness checking. Has anyone ever looked into this, and would you be opposed to (me) adding some? Not necessarily a full blown typing of everything, but at least some basics.