fix(libdd-trace-obfuscation): cargo clippy fix with all lints by Eldolfin · Pull Request #1947 · DataDog/libdatadog

Eldolfin · 2026-05-05T20:06:03Z

What does this PR do?

Applies a restrictive workspace Clippy/Rust lint config and opts in libdd-trace-obfuscation, fixing the resulting crate-local lints without changing the behavior.

Motivation

Tighten lint coverage incrementally by starting with a single crate.

Additional Notes

How to test the change?

CI passing is sufficient validation.

github-actions · 2026-05-05T20:08:03Z

📚 Documentation Check Results

⚠️ 648 documentation warning(s) found

📦 `libdd-trace-obfuscation` - 648 warning(s)

Updated: 2026-05-11 11:47:02 UTC | Commit: 6b1109c | missing-docs job results

github-actions · 2026-05-05T20:08:54Z

Clippy Allow Annotation Report

Comparing clippy allow annotations between branches:

Base Branch: origin/main
PR Branch: origin/oscarld/restrictive-clippy-on-trace-obfuscation

Summary by Rule

Rule	Base Branch	PR Branch	Change
unwrap_used	8	3	✅ -5 (-62.5%)
Total	8	3	✅ -5 (-62.5%)

Annotation Counts by File

File	Base Branch	PR Branch	Change
`libdd-trace-obfuscation/benches/benchmarks/replace_trace_tags_bench.rs`	0	1	⚠️ +1 (N/A)
`libdd-trace-obfuscation/src/credit_cards.rs`	4	0	✅ -4 (-100.0%)
`libdd-trace-obfuscation/src/ip_address.rs`	3	1	✅ -2 (-66.7%)
`libdd-trace-obfuscation/src/replacer.rs`	1	1	No change (0%)

Annotation Stats by Crate

Crate	Base Branch	PR Branch	Change
`clippy-annotation-reporter`	5	5	No change (0%)
`datadog-ffe-ffi`	1	1	No change (0%)
`datadog-ipc`	21	21	No change (0%)
`datadog-live-debugger`	6	6	No change (0%)
`datadog-live-debugger-ffi`	10	10	No change (0%)
`datadog-profiling-replayer`	4	4	No change (0%)
`datadog-remote-config`	3	3	No change (0%)
`datadog-sidecar`	57	57	No change (0%)
`libdd-common`	13	13	No change (0%)
`libdd-common-ffi`	12	12	No change (0%)
`libdd-data-pipeline`	5	5	No change (0%)
`libdd-ddsketch`	2	2	No change (0%)
`libdd-dogstatsd-client`	1	1	No change (0%)
`libdd-profiling`	13	13	No change (0%)
`libdd-telemetry`	20	20	No change (0%)
`libdd-tinybytes`	4	4	No change (0%)
`libdd-trace-normalization`	2	2	No change (0%)
`libdd-trace-obfuscation`	8	3	✅ -5 (-62.5%)
`libdd-trace-stats`	1	1	No change (0%)
`libdd-trace-utils`	15	15	No change (0%)
Total	203	198	✅ -5 (-2.5%)

About This Report

This 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.

github-actions · 2026-05-05T20:09:55Z

🔒 Cargo Deny Results

⚠️ 4 issue(s) found, showing only errors (advisories, bans, sources)

📦 `libdd-trace-obfuscation` - 4 error(s)

Show output

error[unsound]: Rand is unsound with a custom logger using `rand::rng()`
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:182:1
    │
182 │ rand 0.8.5 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
    │
    ├ ID: RUSTSEC-2026-0097
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0097
    ├ It has been reported (by @lopopolo) that the `rand` library is [unsound](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#soundness-of-code--of-a-library) (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met:
      
      - The `log` and `thread_rng` features are enabled
      - A [custom logger](https://docs.rs/log/latest/log/#implementing-a-logger) is defined
      - The custom logger accesses `rand::rng()` (previously `rand::thread_rng()`) and calls any `TryRng` (previously `RngCore`) methods on `ThreadRng`
      - The `ThreadRng` (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data)
      - Trace-level logging is enabled or warn-level logging is enabled and the random source (the `getrandom` crate) is unable to provide a new seed
      
      `TryRng` (previously `RngCore`) methods for `ThreadRng` use `unsafe` code to cast `*mut BlockRng<ReseedingCore>` to `&mut BlockRng<ReseedingCore>`. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of [aliased mutable references is Undefined Behaviour](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict.
    ├ Announcement: https://github.com/rust-random/rand/pull/1763
    ├ Solution: Upgrade to >=0.10.1 OR <0.10.0, >=0.9.3 OR <0.9.0, >=0.8.6 (try `cargo update -p rand`)
    ├ rand v0.8.5
      ├── (dev) libdd-common v4.0.0
      │   ├── libdd-capabilities-impl v1.0.0
      │   │   └── libdd-trace-utils v3.0.1
      │   │       ├── libdd-trace-obfuscation v2.1.0
      │   │       └── (dev) libdd-trace-utils v3.0.1 (*)
      │   ├── libdd-trace-obfuscation v2.1.0 (*)
      │   └── libdd-trace-utils v3.0.1 (*)
      ├── (dev) libdd-trace-normalization v2.0.0
      │   └── libdd-trace-utils v3.0.1 (*)
      ├── libdd-trace-utils v3.0.1 (*)
      └── proptest v1.5.0
          └── (dev) libdd-tinybytes v1.1.0
              ├── (dev) libdd-tinybytes v1.1.0 (*)
              └── libdd-trace-utils v3.0.1 (*)

error[vulnerability]: Name constraints for URI names were incorrectly accepted
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:206:1
    │
206 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0098
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0098
    ├ Name constraints for URI names were ignored and therefore accepted.
      
      Note this library does not provide an API for asserting URI names, and URI name constraints are otherwise not implemented.  URI name constraints are now rejected unconditionally.
      
      Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.
      
      This vulnerability is identified as [GHSA-965h-392x-2mh5](https://github.com/rustls/webpki/security/advisories/GHSA-965h-392x-2mh5). Thank you to @1seal for the report.
    ├ Solution: Upgrade to >=0.103.12, <0.104.0-alpha.1 OR >=0.104.0-alpha.6 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.10
      └── rustls v0.23.37
          ├── hyper-rustls v0.27.7
          │   └── libdd-common v4.0.0
          │       ├── libdd-capabilities-impl v1.0.0
          │       │   └── libdd-trace-utils v3.0.1
          │       │       ├── libdd-trace-obfuscation v2.1.0
          │       │       └── (dev) libdd-trace-utils v3.0.1 (*)
          │       ├── libdd-trace-obfuscation v2.1.0 (*)
          │       └── libdd-trace-utils v3.0.1 (*)
          ├── libdd-common v4.0.0 (*)
          └── tokio-rustls v0.26.0
              ├── hyper-rustls v0.27.7 (*)
              └── libdd-common v4.0.0 (*)

error[vulnerability]: Name constraints were accepted for certificates asserting a wildcard name
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:206:1
    │
206 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0099
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0099
    ├ Permitted subtree name constraints for DNS names were accepted for certificates asserting a wildcard name.
      
      This was incorrect because, given a name constraint of `accept.example.com`, `*.example.com` could feasibly allow a name of `reject.example.com` which is outside the constraint.
      This is very similar to [CVE-2025-61727](https://go.dev/issue/76442).
      
      Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.
      
      This vulnerability is identified as [GHSA-xgp8-3hg3-c2mh](https://github.com/rustls/webpki/security/advisories/GHSA-xgp8-3hg3-c2mh). Thank you to @1seal for the report.
    ├ Solution: Upgrade to >=0.103.12, <0.104.0-alpha.1 OR >=0.104.0-alpha.6 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.10
      └── rustls v0.23.37
          ├── hyper-rustls v0.27.7
          │   └── libdd-common v4.0.0
          │       ├── libdd-capabilities-impl v1.0.0
          │       │   └── libdd-trace-utils v3.0.1
          │       │       ├── libdd-trace-obfuscation v2.1.0
          │       │       └── (dev) libdd-trace-utils v3.0.1 (*)
          │       ├── libdd-trace-obfuscation v2.1.0 (*)
          │       └── libdd-trace-utils v3.0.1 (*)
          ├── libdd-common v4.0.0 (*)
          └── tokio-rustls v0.26.0
              ├── hyper-rustls v0.27.7 (*)
              └── libdd-common v4.0.0 (*)

error[vulnerability]: Reachable panic in certificate revocation list parsing
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:206:1
    │
206 │ rustls-webpki 0.103.10 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0104
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0104
    ├ A panic was reachable when parsing certificate revocation lists via [`BorrowedCertRevocationList::from_der`]
      or [`OwnedCertRevocationList::from_der`].  This was the result of mishandling a syntactically valid empty
      `BIT STRING` appearing in the `onlySomeReasons` element of a `IssuingDistributionPoint` CRL extension.
      
      This panic is reachable prior to a CRL's signature being verified.
      
      Applications that do not use CRLs are not affected.
      
      Thank you to @tynus3 for the report.
    ├ Solution: Upgrade to >=0.103.13, <0.104.0-alpha.1 OR >=0.104.0-alpha.7 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.10
      └── rustls v0.23.37
          ├── hyper-rustls v0.27.7
          │   └── libdd-common v4.0.0
          │       ├── libdd-capabilities-impl v1.0.0
          │       │   └── libdd-trace-utils v3.0.1
          │       │       ├── libdd-trace-obfuscation v2.1.0
          │       │       └── (dev) libdd-trace-utils v3.0.1 (*)
          │       ├── libdd-trace-obfuscation v2.1.0 (*)
          │       └── libdd-trace-utils v3.0.1 (*)
          ├── libdd-common v4.0.0 (*)
          └── tokio-rustls v0.26.0
              ├── hyper-rustls v0.27.7 (*)
              └── libdd-common v4.0.0 (*)

advisories FAILED, bans ok, sources ok

Updated: 2026-05-11 11:48:51 UTC | Commit: 6b1109c | dependency-check job results

codecov-commenter · 2026-05-05T20:20:27Z

Codecov Report

❌ Patch coverage is 74.60317% with 48 lines in your changes missing coverage. Please review.
✅ Project coverage is 72.64%. Comparing base (91fd13c) to head (c352714).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1947      +/-   ##
==========================================
+ Coverage   72.63%   72.64%   +0.01%     
==========================================
  Files         448      448              
  Lines       73582    73585       +3     
==========================================
+ Hits        53444    53458      +14     
+ Misses      20138    20127      -11

Components	Coverage Δ
libdd-crashtracker	`65.05% <ø> (-0.03%)`	⬇️
libdd-crashtracker-ffi	`36.82% <ø> (ø)`
libdd-alloc	`98.77% <ø> (ø)`
libdd-data-pipeline	`86.38% <ø> (-0.21%)`	⬇️
libdd-data-pipeline-ffi	`74.46% <ø> (-1.18%)`	⬇️
libdd-common	`79.81% <ø> (ø)`
libdd-common-ffi	`74.41% <ø> (ø)`
libdd-telemetry	`69.37% <ø> (ø)`
libdd-telemetry-ffi	`19.37% <ø> (ø)`
libdd-dogstatsd-client	`82.64% <ø> (ø)`
datadog-ipc	`76.22% <ø> (ø)`
libdd-profiling	`81.57% <ø> (ø)`
libdd-profiling-ffi	`64.51% <ø> (ø)`
libdd-sampling	`97.25% <ø> (ø)`
datadog-sidecar	`29.26% <ø> (-0.58%)`	⬇️
datdog-sidecar-ffi	`10.48% <ø> (-2.74%)`	⬇️
spawn-worker	`54.69% <ø> (ø)`
libdd-tinybytes	`93.16% <ø> (ø)`
libdd-trace-normalization	`81.71% <ø> (ø)`
libdd-trace-obfuscation	`88.91% <74.60%> (+1.64%)`	⬆️
libdd-trace-protobuf	`68.25% <ø> (ø)`
libdd-trace-utils	`89.27% <ø> (ø)`
libdd-tracer-flare	`86.88% <ø> (ø)`
libdd-log	`74.83% <ø> (ø)`

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

datadog-prod-us1-5 · 2026-05-05T20:20:46Z

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage (details)
• Patch Coverage: 82.84%
• Overall Coverage: 72.65% (+0.02%)

_{This comment will be updated automatically if new data arrives.

🔗 Commit SHA: c352714 | Docs | Datadog PR Page | Give us feedback!}

dd-octo-sts · 2026-05-05T20:37:51Z

Artifact Size Benchmark Report

aarch64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so	7.57 MB	7.57 MB	0% (0 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a	81.66 MB	81.67 MB	+0% (+688 B) 👌

aarch64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a	97.84 MB	97.84 MB	+0% (+1.25 KB) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so	10.01 MB	10.01 MB	0% (0 B) 👌

libdatadog-x64-windows

Artifact	Baseline	Commit	Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll	24.40 MB	24.40 MB	0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib	79.87 KB	79.87 KB	0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb	179.62 MB	179.62 MB	-0% (-8.00 KB) 👌
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib	910.67 MB	910.76 MB	+.01% (+99.05 KB) 🔍
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll	7.71 MB	7.71 MB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib	79.87 KB	79.87 KB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb	23.11 MB	23.11 MB	0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib	45.25 MB	45.25 MB	-0% (-134 B) 👌

libdatadog-x86-windows

Artifact	Baseline	Commit	Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll	21.02 MB	21.02 MB	+.02% (+6.00 KB) 🔍
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib	81.11 KB	81.11 KB	0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb	183.74 MB	183.76 MB	+.01% (+24.00 KB) 🔍
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib	896.93 MB	897.05 MB	+.01% (+128.65 KB) 🔍
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll	5.98 MB	5.98 MB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib	81.11 KB	81.11 KB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb	24.74 MB	24.74 MB	0% (0 B) 👌
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib	42.75 MB	42.75 MB	-0% (-122 B) 👌

x86_64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a	72.78 MB	72.78 MB	+0% (+6.68 KB) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so	8.41 MB	8.41 MB	0% (0 B) 👌

x86_64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a	90.53 MB	90.53 MB	-0% (-96 B) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so	10.03 MB	10.03 MB	0% (0 B) 👌

…, semver)

… and nightly

….1.0

Eldolfin · 2026-05-07T16:19:58Z

 [package]
 name = "libdd-trace-obfuscation"
-version = "2.0.0"
+version = "2.1.0"


Where did this come from? The current released version is 2.0.0. @iunanua any idea?

Reverted. 🫣

Looking closer, adding the #[must_use] to fix the clippy::must_use_candidate attribute is considered a breaking change from the semver checks perspective.

This reverts commit e085bb0.

fix(libdd-trace-obfuscation): cargo clippy fix with all lints

8937e2b

github-actions Bot added the mini-agent label May 5, 2026

Eldolfin commented May 5, 2026

View reviewed changes

Comment thread libdd-trace-obfuscation/src/ip_address.rs Outdated

Eldolfin added 2 commits May 5, 2026 22:40

fix(libdd-trace-obfuscation): cargo clippy llm pass 1

efd9e87

fix(libdd-trace-obfuscation): cargo clippy llm pass 2

bb56e9b

Eldolfin force-pushed the oscarld/restrictive-clippy-on-trace-obfuscation branch from ca1e0f5 to bb56e9b Compare May 5, 2026 20:40

Eldolfin and others added 8 commits May 6, 2026 14:31

feat(clippy): use warn instead of deny, temp allow some lints

b78d263

fix(libdd-trace-obfuscation): cargo clippy llm pass 3

14213c2

fix(libdd-trace-obfuscation): remove now redundant lints in lib.rs

38d5837

fix(clippy): allow some lints which make the code harder to understand

88d11fe

fix(clippy): add codeowners to clippy config

6a27b69

fix: revert map_or_else lint fix

293605d

fix(libdd-trace-obfuscation): remove all easy unwraps

564eca3

Merge branch 'main' into oscarld/restrictive-clippy-on-trace-obfuscation

cb549cf

github-actions Bot added the ci-build label May 7, 2026

Eldolfin and others added 5 commits May 7, 2026 13:58

Merge branch 'main' into oscarld/restrictive-clippy-on-trace-obfuscation

3d6dc3d

fix: llm pass 4 on tests/bench

bbc5099

fix(libdd-trace-obfuscation): fix CI failures (rustfmt, clippy 1.84.1…

162391b

…, semver)

fix(libdd-trace-obfuscation): fix clippy compat across 1.84.1, stable…

fad877f

… and nightly

fix(libdd-trace-obfuscation): update Cargo.lock for version bump to 2…

158bb5d

….1.0

Eldolfin commented May 7, 2026

View reviewed changes

Eldolfin marked this pull request as ready for review May 7, 2026 16:20

Eldolfin requested review from a team as code owners May 7, 2026 16:20

duncanista approved these changes May 7, 2026

View reviewed changes

Eldolfin and others added 3 commits May 7, 2026 23:02

fix(libdd-trace-obfuscation): revert random version bump

e085bb0

Revert "fix(libdd-trace-obfuscation): revert random version bump"

b4c7349

This reverts commit e085bb0.

Merge branch 'main' into oscarld/restrictive-clippy-on-trace-obfuscation

c352714

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(libdd-trace-obfuscation): cargo clippy fix with all lints#1947

fix(libdd-trace-obfuscation): cargo clippy fix with all lints#1947
Eldolfin wants to merge 19 commits into
mainfrom
oscarld/restrictive-clippy-on-trace-obfuscation

Eldolfin commented May 5, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented May 5, 2026 •

edited

Loading

Uh oh!

Uh oh!

github-actions Bot commented May 5, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented May 5, 2026 •

edited

Loading

Uh oh!

codecov-commenter commented May 5, 2026 •

edited

Loading

Uh oh!

datadog-prod-us1-5 Bot commented May 5, 2026 •

edited by datadog-datadog-prod-us1-2 Bot

Loading

Uh oh!

dd-octo-sts Bot commented May 5, 2026 •

edited

Loading

Uh oh!

Eldolfin May 7, 2026

Uh oh!

ekump May 7, 2026

Uh oh!

Eldolfin May 7, 2026

Uh oh!

Eldolfin May 11, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

Eldolfin commented May 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What does this PR do?

Motivation

Additional Notes

How to test the change?

Uh oh!

github-actions Bot commented May 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📚 Documentation Check Results

📦 libdd-trace-obfuscation - 648 warning(s)

Uh oh!

Uh oh!

github-actions Bot commented May 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Clippy Allow Annotation Report

Summary by Rule

Annotation Counts by File

Annotation Stats by Crate

About This Report

Uh oh!

github-actions Bot commented May 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔒 Cargo Deny Results

📦 libdd-trace-obfuscation - 4 error(s)

Uh oh!

codecov-commenter commented May 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

datadog-prod-us1-5 Bot commented May 5, 2026 • edited by datadog-datadog-prod-us1-2 Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dd-octo-sts Bot commented May 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Artifact Size Benchmark Report

Uh oh!

Eldolfin May 7, 2026

Choose a reason for hiding this comment

Uh oh!

ekump May 7, 2026

Choose a reason for hiding this comment

Uh oh!

Eldolfin May 7, 2026

Choose a reason for hiding this comment

Uh oh!

Eldolfin May 11, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Eldolfin commented May 5, 2026 •

edited

Loading

github-actions Bot commented May 5, 2026 •

edited

Loading

📦 `libdd-trace-obfuscation` - 648 warning(s)

github-actions Bot commented May 5, 2026 •

edited

Loading

github-actions Bot commented May 5, 2026 •

edited

Loading

📦 `libdd-trace-obfuscation` - 4 error(s)

codecov-commenter commented May 5, 2026 •

edited

Loading

datadog-prod-us1-5 Bot commented May 5, 2026 •

edited by datadog-datadog-prod-us1-2 Bot

Loading

dd-octo-sts Bot commented May 5, 2026 •

edited

Loading