asyncio: fix duplicate instrumentation#3408
Merged
aabmass merged 16 commits intoopen-telemetry:mainfrom Apr 15, 2025
Merged
Conversation
Contributor
|
@bourbonkk looks like you commited with multiple accounts and one has not signed the CLA |
bourbonkk
commented
Apr 4, 2025
yonathan-wolloch-lendbuzz
approved these changes
Apr 7, 2025
Contributor
Author
|
@xrmx |
aabmass
reviewed
Apr 10, 2025
xrmx
reviewed
Apr 10, 2025
aabmass
approved these changes
Apr 10, 2025
Member
aabmass
left a comment
There was a problem hiding this comment.
I don't want to block this since it's an improvement. Please just address comments
…memory-leak # Conflicts: # CHANGELOG.md
aabmass
approved these changes
Apr 15, 2025
…telemetry/instrumentation/asyncio/instrumentation_state.py
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.
Description
This PR addresses duplicate instrumentation of Future objects when using AsyncioInstrumentor multiple times on the same Future. Without proper de-duplication, callbacks can continue to accumulate and cause memory leaks. This change introduces a simple attribute check on each Future, coroutine, or function so that once instrumented, no additional callbacks or spans will be attached.
Fixes #3383 aiokafka instrumentation cause memory leak
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Does This PR Require a Core Repo Change?
Checklist:
See contributing.md for styleguide, changelog guidelines, and more.