feat(ffe): add __dd_allocation_key metadata to ResolutionDetails#1940
Conversation
Clippy Allow Annotation ReportComparing clippy allow annotations between branches:
Summary by Rule
Annotation Counts by File
Annotation Stats by Crate
About This ReportThis report tracks Clippy allow annotations for specific rules, showing how they've changed in this PR. Decreasing the number of these annotations generally improves code quality. |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #1940 +/- ##
==========================================
- Coverage 71.73% 71.64% -0.09%
==========================================
Files 434 434
Lines 70395 70408 +13
==========================================
- Hits 50497 50447 -50
- Misses 19898 19961 +63
🚀 New features to boost your workflow:
|
🎉 All green!❄️ No new flaky tests detected 🎯 Code Coverage (details) 🔗 Commit SHA: 53a1543 | Docs | Datadog PR Page | Give us feedback! |
Artifact Size Benchmark Reportaarch64-alpine-linux-musl
aarch64-unknown-linux-gnu
libdatadog-x64-windows
libdatadog-x86-windows
x86_64-alpine-linux-musl
x86_64-unknown-linux-gnu
|
leoromanovsky
left a comment
There was a problem hiding this comment.
anything to add to the json test fixtures?
As Sameeran found, the tracers are currently unaligned an what metadata they attach. It's also an internal detail But... it's a good idea to add allocation assertions to system tests |
| inner, | ||
| error_message, | ||
| extra_logging, | ||
| flag_metadata, |
There was a problem hiding this comment.
Oh nice, it makes sense to do this here given that we were already passing flag metadata
# What does this PR do? Remove `extra_logging` handling. # Motivation It was a leftover from migration and was never used. It is also never emitted by the backend. # Additional Notes Stacked on top of #1940 to avoid merge conflicts. # How to test the change? Co-authored-by: oleksii.shmalko <[email protected]>
What does this PR do?
Add
__dd_allocation_keymetadata toResolutionDetails.Motivation
Follow-up from DataDog/dd-trace-rb#5599 (comment)
Additional Notes
How to test the change?