refactor(layers/dtrace): split dtrace layer into separate crate#7078
Merged
koushiro merged 1 commit intoapache:mainfrom Dec 21, 2025
Merged
refactor(layers/dtrace): split dtrace layer into separate crate#7078koushiro merged 1 commit intoapache:mainfrom
koushiro merged 1 commit intoapache:mainfrom
Conversation
dosubot
bot
added
size:M
koushiro
reviewed
Dec 20, 2025
Contributor
Author
|
Thank you for the review. I have made the changes. I didn't knew dtrace is available only on Linux. |
koushiro
approved these changes
Dec 21, 2025
Member
koushiro
left a comment
koushiro
left a comment
There was a problem hiding this comment.
Thanks for your contribution
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
2 participants
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.
Which issue does this PR close?
Closes #6935
Rationale for this change
Relates to #6829
What changes are included in this PR?
This PR extracts the dtrace layer implementation from
opendal-coreinto a standalone crateopendal-layer-dtrace, while keeping the public surfaceopendal::layers::DtraceLayerunchanged.layers-dtraceintact.probe) to the new layer crate.opendal-core.Are there any user-facing changes?
No user-facing changes. The public API
opendal::layers::DtraceLayerremains unchanged.AI Usage Statement
No AI has been used