fix(profiling): better autoinject detection#9904
Conversation
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
|
7441ae3 to
61a2f15
Compare
Datadog ReportBranch report: ✅ 0 Failed, 122120 Passed, 56300 Skipped, 3h 55m 46.05s Total duration (5h 20m 19.43s time saved) |
de372ba to
00b1a64
Compare
00b1a64 to
5a48fd7
Compare
Kyle-Verhoog
left a comment
There was a problem hiding this comment.
just one thought, otherwise good to me!
5a48fd7 to
cf467b4
Compare
f8700dc to
778da61
Compare
778da61 to
1ac1a6c
Compare
BenchmarksBenchmark execution time: 2024-08-07 13:32:43 Comparing candidate commit 920c8e7 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 214 metrics, 2 unstable metrics. |
…hub.com:DataDog/dd-trace-py into 07-23-fix_profiling_better_autoinject_detection
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9904 +/- ##
===========================================
- Coverage 73.57% 10.55% -63.03%
===========================================
Files 1421 1381 -40
Lines 131945 129203 -2742
===========================================
- Hits 97078 13635 -83443
- Misses 34867 115568 +80701 ☔ View full report in Codecov by Sentry. |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.9 2.9
# Navigate to the new working tree
cd .worktrees/backport-2.9
# Create a new branch
git switch --create backport-9904-to-2.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d638a7b92d1ef01b78fad6cb1d44c27543c47059
# Push it to GitHub
git push --set-upstream origin backport-9904-to-2.9
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.9Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.10 2.10
# Navigate to the new working tree
cd .worktrees/backport-2.10
# Create a new branch
git switch --create backport-9904-to-2.10
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d638a7b92d1ef01b78fad6cb1d44c27543c47059
# Push it to GitHub
git push --set-upstream origin backport-9904-to-2.10
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.10Then, create a pull request where the |
Previously, Profiling was injecting its own configuration during lib-injection handling. This was actually a little brittle. Instead, we move to a model where the profiler detects (in its normal configuration) whether the library was injected. Hopefully this is more durable and correct. ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [X] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting) (cherry picked from commit d638a7b)
Backport d638a7b from #9904 to 2.11. [PROF-10280] Previously, Profiling was injecting its own configuration during lib-injection handling. This was actually a little brittle. Instead, we move to a model where the profiler detects (in its normal configuration) whether the library was injected. Hopefully this is more durable and correct. ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [x] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting) [PROF-10280]: https://datadoghq.atlassian.net/browse/PROF-10280?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ Co-authored-by: David Sanchez <[email protected]>

PROF-10280
Previously, Profiling was injecting its own configuration during lib-injection handling. This was actually a little brittle.
Instead, we move to a model where the profiler detects (in its normal configuration) whether the library was injected. Hopefully this is more durable and correct.
Checklist
Reviewer Checklist