Uh oh!
There was an error while loading. Please reload this page.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When multiple application threads finish spans or start traces while the queue is full, both callbacks can read the same
_dropped_countvalue before either stores its increment, causing the public metric to undercount dropped telemetry; this is especially reachable on free-threaded Python builds and other interpreters because+=is not an atomic counter operation. Protect both increments and reads with a shared lock or another thread-safe counter, and cover the interleaving with a controlled concurrency test rather than only the sequential test.AGENTS.md reference: AGENTS.md:L149-L149
Useful? React with 👍 / 👎.