Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ignore NoopMeter from child Registry #1443

Conversation

jake-at-work
Copy link

@jake-at-work jake-at-work commented May 30, 2019

If a child Registry returns a NoopMeter then don't add it to the map of
child Meters.

See #1441

If a child Registry returns a NoopMeter then don't add it to the map of
child Meters.
@shakuzen shakuzen changed the title #1441: Ignore NoopMeter from child Registry. Ignore NoopMeter from child Registry Jun 17, 2019
@shakuzen
Copy link
Member

shakuzen commented Mar 3, 2022

We're reviewing this after looking at #1442. Am I understanding correctly that you are proposing one or the other as a solution to #1441?

@pivotal-cla
Copy link

@pivotal-jbarrett Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@pivotal-cla
Copy link

@pivotal-jbarrett Thank you for signing the Contributor License Agreement!

@jake-at-work
Copy link
Author

jake-at-work commented Mar 3, 2022

I honestly can't recall why from nearly 3 years ago. I think it has to do with the registry holding references multiple references to NoopMeter instances. these two PRs are solutions to the same issue. Sorry I can't be of more help anymore. Since they aren't a concern for my downstream projects as far as I can tell anymore I suppose we can just close them both.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants