-
Notifications
You must be signed in to change notification settings - Fork 306
Notify listeners when the scope top changes after switching scope stacks #8797
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
Merged
mcculls
merged 1 commit into
master
from
mcculls/notify-listeners-when-swapping-scope-stacks
May 12, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
we call before and after on a row without doing anything in between. Can this be simplified ?
Uh oh!
There was an error while loading. Please reload this page.
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.
There's a very subtle difference -
beforeActivated
calls the profiling integration, whileafterActivated
calls the registered listeners.In one place in the code
beforeActivated
is called before changing the top value:dd-trace-java/dd-trace-core/src/main/java/datadog/trace/core/scopemanager/ScopeStack.java
Lines 69 to 76 in e8a2156
but in another part of the code, they are called at the same time after the top has changed:
dd-trace-java/dd-trace-core/src/main/java/datadog/trace/core/scopemanager/ScopeStack.java
Lines 58 to 59 in e8a2156
In terms of actual implementation the profiling integration is just clearing some caches, so there is flexibility here and this could all be done in one method as long as the profiling integration is always called first.
However since the profiling integration will need to be refactored to make it context-first, that's something I will do in a separate PR.