Repository navigation
fix(native): bump libdatadog to v36 - #18713
VianneyRuhlmann wants to merge 4 commits into
Conversation
|
Codeowners resolved as |
BenchmarksBenchmark execution time: 2026-06-24 11:39:58 Comparing candidate commit 92096b1 in PR branch Found 0 performance improvements and 8 performance regressions! Performance is the same for 608 metrics, 10 unstable metrics. scenario:iast_aspects-re_expand_aspect
scenario:iast_aspects-re_search_aspect
scenario:iastaspects-strip_aspect
scenario:iastaspects-upper_noaspect
scenario:iastaspectsospath-ospathbasename_aspect
scenario:span-start
scenario:telemetryaddmetric-1-count-metric-1-times
scenario:tracer-small
|
## Motivation PR #18713 bumps libdatadog to v36. System Tests fail because invalid Feature Flagging and Experimentation flag configuration now comes through libdatadog as `FlagConfigurationInvalid`; dd-trace-py previously fell through to OpenFeature `GENERAL`, causing metrics to emit `error.type:general` instead of the expected `error.type:parse_error`. ## Changes This maps `EvaluationError::FlagConfigurationInvalid` to the existing native `ParseError` wrapper path alongside `ConfigurationParseError`. It also adds an OpenFeature provider regression test for invalid per-flag configuration and a release note for the preserved error-code behavior. ## Decisions The fix stays in the Rust/PyO3 wrapper rather than changing Python metrics code or system-test expectations, because the upstream native error still represents an invalid flag configuration parse/compile failure. This PR is stacked on `vianney/bump-libdatadog-36` so the libdatadog upgrade can absorb the compatibility shim directly. ## Testing - `scripts/lint fmt tests/openfeature/test_provider.py` - `cargo fmt --manifest-path src/native/Cargo.toml -- src/native/ffe.rs` - `scripts/lint style tests/openfeature/test_provider.py` - `scripts/run-tests --venv 13c4b39 tests/openfeature/test_provider.py -- -- -k invalid_configuration -vv` - `uvx --from reno reno lint` ## Risks Low. The change only maps a newly introduced libdatadog v36 FFE error variant to the same OpenFeature parse error already used for configuration parse failures.
|
Would it make sense to merge this PR instead: #18821? Then we can bump dd-trace-py straight to v37 rather than v36. |
|
Closed in favor of #18821 |
Description
Bump libdatadog to v36.0.0