Skip to content

feat(ffe): add bounded non-waiting evaluation submission - #2614

Draft
vjfridge wants to merge 9 commits into
vickie/FFL-3198/native-flagevaluation-piifrom
vickie/FFL-3198/bounded-flagevaluation-handoff
Draft

feat(ffe): add bounded non-waiting evaluation submission#2614
vjfridge wants to merge 9 commits into
vickie/FFL-3198/native-flagevaluation-piifrom
vickie/FFL-3198/bounded-flagevaluation-handoff

Conversation

@vjfridge

@vjfridge vjfridge commented Oct 2, 2026 •
edited by atlassian Bot
Loading

Copy link
Copy Markdown
Contributor

What does this PR do?

Adds a non-waiting native handoff for one flagevaluation track EVP observation. This is PR 2 of the PHP implementation sequence, stacked on #2605.

  • PR 1 (feat(ffe): protect PII in native flagevaluation events #2605): native privacy handling, aggregation, and EVP output.
  • This PR: check whether the existing sidecar transport can accept an observation before copying its data, then attempt submission without waiting or reconnecting.
  • Next PHP PR: capture the evaluation result and privacy setting, call this interface, and connect configuration, lifecycle, and diagnostics.

Motivation

Sending evaluation telemetry should not make a customer's flag evaluation wait for the sidecar. This provides the native interface PHP needs to skip telemetry work when the transport is unavailable or overloaded, while preserving the privacy rules from the cross-SDK guidance.

Tracking: FFL-3198.

Additional Notes

Key decisions

  • Reuse the existing sidecar transport, shared outstanding-message limit, overload shedding, and priority-message ordering. No new worker, queue, retry buffer, or IPC action.
  • Recheck admission during submission: an earlier readiness check does not reserve capacity. Rejected observations are not retained.
  • Protected observations do not inspect or copy evaluation context. With consent, inspect only the first 256 scalar entries; invalid entries consume slots, and overlength fields are omitted.
  • Keep hashing, aggregation, final privacy checks, and HTTP delivery in the sidecar. Submission success means local transport acceptance, not confirmed delivery.
  • Reject oversized observations without disabling a healthy connection, including when the operating system's packet limit is lower than the advertised IPC limit.

Blast radius and limitations

  • Adds an opt-in C interface; PHP does not call it yet. Existing batch callers and other sidecar producers retain their behavior.
  • The new IPC send variant is used only by this FFE path. No shared protocol negotiation or wire-layout change is introduced here.
  • Bounded context and a message-count limit are not a total queue-memory byte budget. Consented context still requires work on the calling thread.
  • Preliminary native measurements before the final packet-rejection fix sustained 10,000 attempts/sec for protected and 10-field contexts. The 256-field fixture reached about 2,900–3,100/sec under one-/two-CPU quotas. These are isolated native measurements, not PHP request-latency results or a no-regression claim.

How to test the change?

  • Native suites: 341 passed, one existing skip across IPC, FFE, sidecar, and sidecar FFI; formatting, Clippy, and five doc tests passed.
  • Real-socket and receiver-to-HTTP tests cover rejection-before-copy, overload/ACK recovery, priority ordering, ownership, protected/consented payloads, safe logs, and oversized-packet recovery.
  • Generic C/C++ FFI examples passed 13 tests, with two existing skips, before the final IPC rejection fix. This does not validate the new sidecar C header.

Remaining before ready for review/merge

  • Validate the generated sidecar C header and linked smoke fixture. Local generation hits an empty ddog_Option_U64_Tag enum; the same failure was reproduced on parent commit 5076a9b7d. The fixture is added but has not passed.
  • Complete Windows/macOS validation and inspect this PR's CI results; local validation is Linux ARM64 only.
  • Refresh the native performance measurements on the final commit and assess the large-consented-context cost.
  • After feat(ffe): protect PII in native flagevaluation events #2605 merges, update this stacked branch and retarget to main. Merging is handled manually by the author.

PHP system-tests and ffe-dogfooding belong to the subsequent PHP integration PR, not to the native-only validation above.

@github-actions

github-actions Bot commented Oct 2, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

🔒 Cargo Deny Results

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

📦 datadog-sidecar-ffi - 4 error(s)

Show output 
error[unmaintained]: Bincode is unmaintained
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:35:1
   │
35 │ bincode 1.3.3 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unmaintained advisory detected
   │
   ├ ID: RUSTSEC-2025-0141
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2025-0141
   ├ Due to a doxxing and harassment incident, the bincode team has taken the decision to cease development permanently.
     
     The team considers version 1.3.3 a complete version of bincode that is not in need of any updates.
     
     ## Alternatives to consider
     
     * [wincode](https://crates.io/crates/wincode)
     * [postcard](https://crates.io/crates/postcard)
     * [bitcode](https://crates.io/crates/bitcode)
     * [rkyv](https://crates.io/crates/rkyv)
   ├ Announcement: https://git.sr.ht/~stygianentity/bincode/tree/v3.0/item/README.md
   ├ Solution: No safe upgrade is available!
   ├ bincode v1.3.3
     ├── datadog-sidecar v0.0.1
     │   └── datadog-sidecar-ffi v0.0.1
     ├── (dev) libdd-ffe v2.0.0
     │   └── datadog-sidecar v0.0.1 (*)
     └── libdd-ipc v2.0.0
         ├── datadog-sidecar v0.0.1 (*)
         └── datadog-sidecar-ffi v0.0.1 (*)

error[unsound]: Potential use-after-free due to lack of panic safety in `LruCache::pop()`
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:232:1
    │
232 │ lru 0.16.4 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
    │
    ├ ID: RUSTSEC-2026-0253
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0253
    ├ `LruCache::pop()` in `lru` was not panic-safe. If the `Drop` implementation of a stored key panics during `pop()`, `self.detach()` is never called, leaving dangling pointers in the internal doubly-linked list.
      
      A subsequent cache operation that triggers eviction can then dereference these dangling pointers:
      - The node is freed from the map, but remains linked in the LRU list due to the skipped `detach()` call
      - When a new insertion causes eviction, the LRU traversal encounters the dangling pointer
      - This results in a write to already-freed memory during the eviction process
      
      ## Impact
      
      - **CWE-416 (Use-After-Free):** memory corruption when subsequent cache operations access freed node pointers in the linked list
      - **CWE-415 (Double Free):** potential heap corruption when the same memory is freed multiple times
      
      Both types of undefined behavior can be invoked in safe Rust, but only if unwinding panics are enabled and `std::panic::catch_unwind` is used with key types that have potentially-panicking `Drop` implementations.
      
      ## Fix
      
      Fixed in `lru` 0.18.2 by detaching the node from the linked list before freeing it and dropping the key ([lru-rs#238](https://github.com/jeromefroe/lru-rs/pull/238)).
    ├ Announcement: https://github.com/jeromefroe/lru-rs/pull/238
    ├ Solution: Upgrade to >=0.18.2 (try `cargo update -p lru`)
    ├ lru v0.16.4
      └── libdd-ffe v2.0.0
          └── datadog-sidecar v0.0.1
              └── datadog-sidecar-ffi v0.0.1

error[unmaintained]: paste - no longer maintained
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:275:1
    │
275 │ paste 1.0.15 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unmaintained advisory detected
    │
    ├ ID: RUSTSEC-2024-0436
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2024-0436
    ├ The creator of the crate `paste` has stated in the [`README.md`](https://github.com/dtolnay/paste/blob/master/README.md) 
      that this project is not longer maintained as well as archived the repository
      
      ## Possible Alternative(s)
      
      - [`pastey`]: a fork of paste and is aimed to be a drop-in replacement with additional features for paste crate
      - [`with_builtin_macros`]: crate providing a [superset of `paste`'s functionality including general `macro_rules!` eager expansions](https://docs.rs/with_builtin_macros/0.1.0/with_builtin_macros/macro.with_eager_expansions.html)  and `concat!`/`concat_idents!` macros
      
      [`pastey`]: https://crates.io/crates/pastey
      [`with_builtin_macros`]: https://crates.io/crates/with_builtin_macros
    ├ Announcement: https://github.com/dtolnay/paste
    ├ Solution: No safe upgrade is available!
    ├ paste v1.0.15
      ├── libdd-libunwind-sys v1.0.3
      │   └── libdd-crashtracker v3.0.0
      │       ├── datadog-sidecar v0.0.1
      │       │   └── datadog-sidecar-ffi v0.0.1
      │       ├── datadog-sidecar-ffi v0.0.1 (*)
      │       └── libdd-crashtracker-ffi v44.0.0
      │           ├── datadog-sidecar v0.0.1 (*)
      │           └── datadog-sidecar-ffi v0.0.1 (*)
      ├── libdd-telemetry-ffi v44.0.0
      │   └── datadog-sidecar-ffi v0.0.1 (*)
      └── rmp v0.8.14
          ├── libdd-trace-utils v14.0.0
          │   ├── (dev) datadog-sidecar v0.0.1 (*)
          │   ├── (dev) datadog-sidecar-ffi v0.0.1 (*)
          │   ├── libdd-data-pipeline v12.0.0
          │   │   ├── datadog-sidecar v0.0.1 (*)
          │   │   └── libdd-live-debugger v1.0.0
          │   │       ├── datadog-sidecar v0.0.1 (*)
          │   │       └── datadog-sidecar-ffi v0.0.1 (*)
          │   ├── libdd-data-pipeline-core v3.0.0
          │   │   └── libdd-data-pipeline v12.0.0 (*)
          │   ├── libdd-trace-obfuscation v10.0.0
          │   │   ├── libdd-data-pipeline v12.0.0 (*)
          │   │   ├── libdd-data-pipeline-core v3.0.0 (*)
          │   │   └── libdd-trace-stats v11.0.0
          │   │       ├── datadog-sidecar v0.0.1 (*)
          │   │       ├── libdd-data-pipeline v12.0.0 (*)
          │   │       └── libdd-ipc v2.0.0
          │   │           ├── datadog-sidecar v0.0.1 (*)
          │   │           └── datadog-sidecar-ffi v0.0.1 (*)
          │   ├── libdd-trace-stats v11.0.0 (*)
          │   └── (dev) libdd-trace-utils v14.0.0 (*)
          ├── rmp-serde v1.3.0
          │   ├── datadog-sidecar-ffi v0.0.1 (*)
          │   ├── libdd-data-pipeline v12.0.0 (*)
          │   ├── (dev) libdd-tinybytes v1.1.5
          │   │   ├── datadog-sidecar v0.0.1 (*)
          │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
          │   │   ├── libdd-data-pipeline v12.0.0 (*)
          │   │   ├── (dev) libdd-data-pipeline-core v3.0.0 (*)
          │   │   ├── libdd-ipc v2.0.0 (*)
          │   │   ├── (dev) libdd-tinybytes v1.1.5 (*)
          │   │   ├── (dev) libdd-trace-obfuscation v10.0.0 (*)
          │   │   └── libdd-trace-utils v14.0.0 (*)
          │   ├── libdd-trace-stats v11.0.0 (*)
          │   └── libdd-trace-utils v14.0.0 (*)
          └── rmpv v1.3.0
              └── libdd-trace-utils v14.0.0 (*)

error[vulnerability]: TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:333:1
    │
333 │ rustls 0.23.37 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0285
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0285
    ├ Rustls accepted TLS 1.3 handshake messages sent at the wrong encryption level
      when they followed a key-changing message in the same record. For example,
      a plaintext `EncryptedExtensions` message packed into the same record as the
      `ServerHello` was accepted.
      
      RFC 8446 section 5.1 requires that handshake messages do not span key changes,
      and that implementations terminate the connection with an "unexpected_message"
      alert if they do.
      
      The handshake transcript is still authenticated, so a network-position attacker
      cannot use this to alter or complete a handshake; the practical effect is that
      a peer could send handshake messages that should be encrypted in plaintext
      without rustls rejecting the connection.
      
      This is functionally the same bug as Go's
      [GO-2026-4340](https://pkg.go.dev/vuln/GO-2026-4340) (CVE-2025-61730).
    ├ Announcement: https://github.com/rustls/rustls/security/advisories/GHSA-2mjx-qc3c-rqvc
    ├ Solution: Upgrade to >=0.23.45 (try `cargo update -p rustls`)
    ├ rustls v0.23.37
      ├── hyper-rustls v0.27.7
      │   └── libdd-common v8.0.0
      │       ├── datadog-sidecar v0.0.1
      │       │   └── datadog-sidecar-ffi v0.0.1
      │       ├── datadog-sidecar-ffi v0.0.1 (*)
      │       ├── libdd-capabilities-impl v7.0.0
      │       │   ├── datadog-sidecar v0.0.1 (*)
      │       │   ├── libdd-crashtracker v3.0.0
      │       │   │   ├── datadog-sidecar v0.0.1 (*)
      │       │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │       │   │   └── libdd-crashtracker-ffi v44.0.0
      │       │   │       ├── datadog-sidecar v0.0.1 (*)
      │       │   │       └── datadog-sidecar-ffi v0.0.1 (*)
      │       │   ├── libdd-data-pipeline v12.0.0
      │       │   │   ├── datadog-sidecar v0.0.1 (*)
      │       │   │   └── libdd-live-debugger v1.0.0
      │       │   │       ├── datadog-sidecar v0.0.1 (*)
      │       │   │       └── datadog-sidecar-ffi v0.0.1 (*)
      │       │   ├── (dev) libdd-ffe v2.0.0
      │       │   │   └── datadog-sidecar v0.0.1 (*)
      │       │   ├── libdd-live-debugger v1.0.0 (*)
      │       │   ├── libdd-remote-config v7.0.0
      │       │   │   ├── (dev) datadog-sidecar v0.0.1 (*)
      │       │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │       │   │   ├── libdd-ffe v2.0.0 (*)
      │       │   │   ├── libdd-live-debugger v1.0.0 (*)
      │       │   │   └── (dev) libdd-remote-config v7.0.0 (*)
      │       │   ├── libdd-shared-runtime v6.0.0
      │       │   │   ├── libdd-data-pipeline v12.0.0 (*)
      │       │   │   ├── libdd-dogstatsd-client v8.0.0
      │       │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │       │   │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │       │   │   │   ├── libdd-data-pipeline v12.0.0 (*)
      │       │   │   │   └── libdd-trace-stats v11.0.0
      │       │   │   │       ├── datadog-sidecar v0.0.1 (*)
      │       │   │   │       ├── libdd-data-pipeline v12.0.0 (*)
      │       │   │   │       └── libdd-ipc v2.0.0
      │       │   │   │           ├── datadog-sidecar v0.0.1 (*)
      │       │   │   │           └── datadog-sidecar-ffi v0.0.1 (*)
      │       │   │   ├── libdd-telemetry v10.0.0
      │       │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │       │   │   │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │       │   │   │   ├── libdd-crashtracker v3.0.0 (*)
      │       │   │   │   ├── libdd-data-pipeline v12.0.0 (*)
      │       │   │   │   ├── libdd-telemetry-ffi v44.0.0
      │       │   │   │   │   └── datadog-sidecar-ffi v0.0.1 (*)
      │       │   │   │   └── libdd-trace-stats v11.0.0 (*)
      │       │   │   └── libdd-trace-stats v11.0.0 (*)
      │       │   ├── (dev) libdd-telemetry v10.0.0 (*)
      │       │   ├── libdd-telemetry-ffi v44.0.0 (*)
      │       │   ├── libdd-trace-stats v11.0.0 (*)
      │       │   └── libdd-trace-utils v14.0.0
      │       │       ├── (dev) datadog-sidecar v0.0.1 (*)
      │       │       ├── (dev) datadog-sidecar-ffi v0.0.1 (*)
      │       │       ├── libdd-data-pipeline v12.0.0 (*)
      │       │       ├── libdd-data-pipeline-core v3.0.0
      │       │       │   └── libdd-data-pipeline v12.0.0 (*)
      │       │       ├── libdd-trace-obfuscation v10.0.0
      │       │       │   ├── libdd-data-pipeline v12.0.0 (*)
      │       │       │   ├── libdd-data-pipeline-core v3.0.0 (*)
      │       │       │   └── libdd-trace-stats v11.0.0 (*)
      │       │       ├── libdd-trace-stats v11.0.0 (*)
      │       │       └── (dev) libdd-trace-utils v14.0.0 (*)
      │       ├── libdd-common-ffi v44.0.0
      │       │   ├── datadog-sidecar v0.0.1 (*)
      │       │   ├── datadog-sidecar-ffi v0.0.1 (*)
      │       │   ├── libdd-crashtracker-ffi v44.0.0 (*)
      │       │   └── libdd-telemetry-ffi v44.0.0 (*)
      │       ├── (build) libdd-crashtracker v3.0.0 (*)
      │       ├── libdd-crashtracker-ffi v44.0.0 (*)
      │       ├── libdd-data-pipeline v12.0.0 (*)
      │       ├── libdd-data-pipeline-core v3.0.0 (*)
      │       ├── libdd-dogstatsd-client v8.0.0 (*)
      │       ├── libdd-ffe v2.0.0 (*)
      │       ├── libdd-ipc v2.0.0 (*)
      │       ├── libdd-live-debugger v1.0.0 (*)
      │       ├── libdd-remote-config v7.0.0 (*)
      │       ├── libdd-shared-runtime v6.0.0 (*)
      │       ├── libdd-telemetry v10.0.0 (*)
      │       ├── libdd-telemetry-ffi v44.0.0 (*)
      │       ├── libdd-trace-obfuscation v10.0.0 (*)
      │       ├── libdd-trace-stats v11.0.0 (*)
      │       └── libdd-trace-utils v14.0.0 (*)
      ├── libdd-common v8.0.0 (*)
      ├── rustls-platform-verifier v0.6.2
      │   └── libdd-common v8.0.0 (*)
      └── tokio-rustls v0.26.0
          └── hyper-rustls v0.27.7 (*)

advisories FAILED, bans ok, sources ok

📦 datadog-sidecar - 3 error(s)

Show output 
error[unmaintained]: Bincode is unmaintained
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:35:1
   │
35 │ bincode 1.3.3 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unmaintained advisory detected
   │
   ├ ID: RUSTSEC-2025-0141
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2025-0141
   ├ Due to a doxxing and harassment incident, the bincode team has taken the decision to cease development permanently.
     
     The team considers version 1.3.3 a complete version of bincode that is not in need of any updates.
     
     ## Alternatives to consider
     
     * [wincode](https://crates.io/crates/wincode)
     * [postcard](https://crates.io/crates/postcard)
     * [bitcode](https://crates.io/crates/bitcode)
     * [rkyv](https://crates.io/crates/rkyv)
   ├ Announcement: https://git.sr.ht/~stygianentity/bincode/tree/v3.0/item/README.md
   ├ Solution: No safe upgrade is available!
   ├ bincode v1.3.3
     ├── datadog-sidecar v0.0.1
     ├── (dev) libdd-ffe v2.0.0
     │   └── datadog-sidecar v0.0.1 (*)
     └── libdd-ipc v2.0.0
         └── datadog-sidecar v0.0.1 (*)

error[unsound]: Potential use-after-free due to lack of panic safety in `LruCache::pop()`
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:230:1
    │
230 │ lru 0.16.4 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
    │
    ├ ID: RUSTSEC-2026-0253
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0253
    ├ `LruCache::pop()` in `lru` was not panic-safe. If the `Drop` implementation of a stored key panics during `pop()`, `self.detach()` is never called, leaving dangling pointers in the internal doubly-linked list.
      
      A subsequent cache operation that triggers eviction can then dereference these dangling pointers:
      - The node is freed from the map, but remains linked in the LRU list due to the skipped `detach()` call
      - When a new insertion causes eviction, the LRU traversal encounters the dangling pointer
      - This results in a write to already-freed memory during the eviction process
      
      ## Impact
      
      - **CWE-416 (Use-After-Free):** memory corruption when subsequent cache operations access freed node pointers in the linked list
      - **CWE-415 (Double Free):** potential heap corruption when the same memory is freed multiple times
      
      Both types of undefined behavior can be invoked in safe Rust, but only if unwinding panics are enabled and `std::panic::catch_unwind` is used with key types that have potentially-panicking `Drop` implementations.
      
      ## Fix
      
      Fixed in `lru` 0.18.2 by detaching the node from the linked list before freeing it and dropping the key ([lru-rs#238](https://github.com/jeromefroe/lru-rs/pull/238)).
    ├ Announcement: https://github.com/jeromefroe/lru-rs/pull/238
    ├ Solution: Upgrade to >=0.18.2 (try `cargo update -p lru`)
    ├ lru v0.16.4
      └── libdd-ffe v2.0.0
          └── datadog-sidecar v0.0.1

error[vulnerability]: TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:331:1
    │
331 │ rustls 0.23.37 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0285
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0285
    ├ Rustls accepted TLS 1.3 handshake messages sent at the wrong encryption level
      when they followed a key-changing message in the same record. For example,
      a plaintext `EncryptedExtensions` message packed into the same record as the
      `ServerHello` was accepted.
      
      RFC 8446 section 5.1 requires that handshake messages do not span key changes,
      and that implementations terminate the connection with an "unexpected_message"
      alert if they do.
      
      The handshake transcript is still authenticated, so a network-position attacker
      cannot use this to alter or complete a handshake; the practical effect is that
      a peer could send handshake messages that should be encrypted in plaintext
      without rustls rejecting the connection.
      
      This is functionally the same bug as Go's
      [GO-2026-4340](https://pkg.go.dev/vuln/GO-2026-4340) (CVE-2025-61730).
    ├ Announcement: https://github.com/rustls/rustls/security/advisories/GHSA-2mjx-qc3c-rqvc
    ├ Solution: Upgrade to >=0.23.45 (try `cargo update -p rustls`)
    ├ rustls v0.23.37
      ├── hyper-rustls v0.27.7
      │   └── libdd-common v8.0.0
      │       ├── datadog-sidecar v0.0.1
      │       ├── libdd-capabilities-impl v7.0.0
      │       │   ├── datadog-sidecar v0.0.1 (*)
      │       │   ├── libdd-crashtracker v3.0.0
      │       │   │   ├── datadog-sidecar v0.0.1 (*)
      │       │   │   └── libdd-crashtracker-ffi v44.0.0
      │       │   │       └── datadog-sidecar v0.0.1 (*)
      │       │   ├── libdd-data-pipeline v12.0.0
      │       │   │   ├── datadog-sidecar v0.0.1 (*)
      │       │   │   └── libdd-live-debugger v1.0.0
      │       │   │       └── datadog-sidecar v0.0.1 (*)
      │       │   ├── (dev) libdd-ffe v2.0.0
      │       │   │   └── datadog-sidecar v0.0.1 (*)
      │       │   ├── libdd-live-debugger v1.0.0 (*)
      │       │   ├── libdd-remote-config v7.0.0
      │       │   │   ├── (dev) datadog-sidecar v0.0.1 (*)
      │       │   │   ├── libdd-ffe v2.0.0 (*)
      │       │   │   ├── libdd-live-debugger v1.0.0 (*)
      │       │   │   └── (dev) libdd-remote-config v7.0.0 (*)
      │       │   ├── libdd-shared-runtime v6.0.0
      │       │   │   ├── libdd-data-pipeline v12.0.0 (*)
      │       │   │   ├── libdd-dogstatsd-client v8.0.0
      │       │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │       │   │   │   ├── libdd-data-pipeline v12.0.0 (*)
      │       │   │   │   └── libdd-trace-stats v11.0.0
      │       │   │   │       ├── datadog-sidecar v0.0.1 (*)
      │       │   │   │       ├── libdd-data-pipeline v12.0.0 (*)
      │       │   │   │       └── libdd-ipc v2.0.0
      │       │   │   │           └── datadog-sidecar v0.0.1 (*)
      │       │   │   ├── libdd-telemetry v10.0.0
      │       │   │   │   ├── datadog-sidecar v0.0.1 (*)
      │       │   │   │   ├── libdd-crashtracker v3.0.0 (*)
      │       │   │   │   ├── libdd-data-pipeline v12.0.0 (*)
      │       │   │   │   └── libdd-trace-stats v11.0.0 (*)
      │       │   │   └── libdd-trace-stats v11.0.0 (*)
      │       │   ├── (dev) libdd-telemetry v10.0.0 (*)
      │       │   ├── libdd-trace-stats v11.0.0 (*)
      │       │   └── libdd-trace-utils v14.0.0
      │       │       ├── (dev) datadog-sidecar v0.0.1 (*)
      │       │       ├── libdd-data-pipeline v12.0.0 (*)
      │       │       ├── libdd-data-pipeline-core v3.0.0
      │       │       │   └── libdd-data-pipeline v12.0.0 (*)
      │       │       ├── libdd-trace-obfuscation v10.0.0
      │       │       │   ├── libdd-data-pipeline v12.0.0 (*)
      │       │       │   ├── libdd-data-pipeline-core v3.0.0 (*)
      │       │       │   └── libdd-trace-stats v11.0.0 (*)
      │       │       ├── libdd-trace-stats v11.0.0 (*)
      │       │       └── (dev) libdd-trace-utils v14.0.0 (*)
      │       ├── libdd-common-ffi v44.0.0
      │       │   ├── datadog-sidecar v0.0.1 (*)
      │       │   └── libdd-crashtracker-ffi v44.0.0 (*)
      │       ├── (build) libdd-crashtracker v3.0.0 (*)
      │       ├── libdd-crashtracker-ffi v44.0.0 (*)
      │       ├── libdd-data-pipeline v12.0.0 (*)
      │       ├── libdd-data-pipeline-core v3.0.0 (*)
      │       ├── libdd-dogstatsd-client v8.0.0 (*)
      │       ├── libdd-ffe v2.0.0 (*)
      │       ├── libdd-ipc v2.0.0 (*)
      │       ├── libdd-live-debugger v1.0.0 (*)
      │       ├── libdd-remote-config v7.0.0 (*)
      │       ├── libdd-shared-runtime v6.0.0 (*)
      │       ├── libdd-telemetry v10.0.0 (*)
      │       ├── libdd-trace-obfuscation v10.0.0 (*)
      │       ├── libdd-trace-stats v11.0.0 (*)
      │       └── libdd-trace-utils v14.0.0 (*)
      ├── libdd-common v8.0.0 (*)
      ├── rustls-platform-verifier v0.6.2
      │   └── libdd-common v8.0.0 (*)
      └── tokio-rustls v0.26.0
          └── hyper-rustls v0.27.7 (*)

advisories FAILED, bans ok, sources ok

📦 libdd-ipc - 2 error(s)

Show output 
error[unmaintained]: Bincode is unmaintained
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:24:1
   │
24 │ bincode 1.3.3 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unmaintained advisory detected
   │
   ├ ID: RUSTSEC-2025-0141
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2025-0141
   ├ Due to a doxxing and harassment incident, the bincode team has taken the decision to cease development permanently.
     
     The team considers version 1.3.3 a complete version of bincode that is not in need of any updates.
     
     ## Alternatives to consider
     
     * [wincode](https://crates.io/crates/wincode)
     * [postcard](https://crates.io/crates/postcard)
     * [bitcode](https://crates.io/crates/bitcode)
     * [rkyv](https://crates.io/crates/rkyv)
   ├ Announcement: https://git.sr.ht/~stygianentity/bincode/tree/v3.0/item/README.md
   ├ Solution: No safe upgrade is available!
   ├ bincode v1.3.3
     └── libdd-ipc v2.0.0

error[vulnerability]: TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:229:1
    │
229 │ rustls 0.23.37 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0285
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0285
    ├ Rustls accepted TLS 1.3 handshake messages sent at the wrong encryption level
      when they followed a key-changing message in the same record. For example,
      a plaintext `EncryptedExtensions` message packed into the same record as the
      `ServerHello` was accepted.
      
      RFC 8446 section 5.1 requires that handshake messages do not span key changes,
      and that implementations terminate the connection with an "unexpected_message"
      alert if they do.
      
      The handshake transcript is still authenticated, so a network-position attacker
      cannot use this to alter or complete a handshake; the practical effect is that
      a peer could send handshake messages that should be encrypted in plaintext
      without rustls rejecting the connection.
      
      This is functionally the same bug as Go's
      [GO-2026-4340](https://pkg.go.dev/vuln/GO-2026-4340) (CVE-2025-61730).
    ├ Announcement: https://github.com/rustls/rustls/security/advisories/GHSA-2mjx-qc3c-rqvc
    ├ Solution: Upgrade to >=0.23.45 (try `cargo update -p rustls`)
    ├ rustls v0.23.37
      ├── hyper-rustls v0.27.7
      │   └── libdd-common v8.0.0
      │       ├── libdd-capabilities-impl v7.0.0
      │       │   ├── libdd-shared-runtime v6.0.0
      │       │   │   └── libdd-trace-stats v11.0.0
      │       │   │       └── libdd-ipc v2.0.0
      │       │   ├── libdd-trace-stats v11.0.0 (*)
      │       │   └── libdd-trace-utils v14.0.0
      │       │       ├── libdd-trace-obfuscation v10.0.0
      │       │       │   └── libdd-trace-stats v11.0.0 (*)
      │       │       ├── libdd-trace-stats v11.0.0 (*)
      │       │       └── (dev) libdd-trace-utils v14.0.0 (*)
      │       ├── libdd-ipc v2.0.0 (*)
      │       ├── libdd-shared-runtime v6.0.0 (*)
      │       ├── libdd-trace-obfuscation v10.0.0 (*)
      │       ├── libdd-trace-stats v11.0.0 (*)
      │       └── libdd-trace-utils v14.0.0 (*)
      ├── libdd-common v8.0.0 (*)
      ├── rustls-platform-verifier v0.6.2
      │   └── libdd-common v8.0.0 (*)
      └── tokio-rustls v0.26.0
          └── hyper-rustls v0.27.7 (*)

advisories FAILED, bans ok, sources ok

Updated: 2026-10-05 16:26:42 UTC | Commit: c05b813 | dependency-check job results

@github-actions

github-actions Bot commented Oct 2, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

📚 Documentation Check Results

⚠️ 7211 documentation warning(s) found

📦 datadog-sidecar-ffi - 3244 warning(s)

📦 datadog-sidecar - 2946 warning(s)

📦 libdd-ipc - 1021 warning(s)

Updated: 2026-10-05 16:28:08 UTC | Commit: c05b813 | missing-docs job results

@pr-commenter

pr-commenter Bot commented Oct 2, 2026 •
edited
Loading

Copy link
Copy Markdown

Benchmarks

Comparison

Benchmark execution time: 2026-10-05 16:56:50

Comparing candidate commit a142ab6 in PR branch vickie/FFL-3198/bounded-flagevaluation-handoff with baseline commit fbdbe43 in branch vickie/FFL-3198/native-flagevaluation-pii.

📊 Benchmarking dashboard

Found 3 performance improvements and 4 performance regressions! Performance is the same for 155 metrics, 0 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

  • 🟩 = significantly better candidate vs. baseline
  • 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

scenario:credit_card/is_card_number_no_luhn/ 3782-8224-6310-005

  • 🟥 execution_time [+2.678µs; +2.956µs] or [+4.315%; +4.763%]
  • 🟥 throughput [-739119.876op/s; -668028.826op/s] or [-4.586%; -4.145%]

scenario:msgpack_decoder::v05/high_sharing/2000

  • 🟩 execution_time [-116.579µs; -116.118µs] or [-6.966%; -6.938%]
  • 🟩 throughput [+89109.011op/s; +89462.810op/s] or [+7.457%; +7.486%]

scenario:vec_map/get_miss/8

  • 🟩 execution_time [-3.396ns; -2.794ns] or [-15.629%; -12.856%]

scenario:vec_map/get_mut/16

  • 🟥 execution_time [+14.811ns; +25.344ns] or [+5.415%; +9.265%]
  • 🟥 throughput [-5130505.045op/s; -3447124.837op/s] or [-8.691%; -5.840%]

Benchmark execution time: 2026-10-05 16:54:49

Comparing candidate commit a142ab6 in PR branch vickie/FFL-3198/bounded-flagevaluation-handoff with baseline commit fbdbe43 in branch vickie/FFL-3198/native-flagevaluation-pii.

📊 Benchmarking dashboard

Found 0 performance improvements and 0 performance regressions! Performance is the same for 92 metrics, 0 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

  • 🟩 = significantly better candidate vs. baseline
  • 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

Benchmark execution time: 2026-10-05 16:52:23

Comparing candidate commit a142ab6 in PR branch vickie/FFL-3198/bounded-flagevaluation-handoff with baseline commit fbdbe43 in branch vickie/FFL-3198/native-flagevaluation-pii.

📊 Benchmarking dashboard

Found 0 performance improvements and 1 performance regressions! Performance is the same for 88 metrics, 10 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

  • 🟩 = significantly better candidate vs. baseline
  • 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

scenario:glob_matcher/ascii_case_insensitive_match/wall_time

  • 🟥 execution_time [+1.564ns; +1.859ns] or [+5.239%; +6.229%]

Unstable benchmarks

These benchmarks have a confidence interval too wide to call a change; treat them as noise rather than signal.

scenario:datadog_sample_span/parent_not_sampled_short_circuit/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+555.542%; -555.644%]

scenario:datadog_sample_span/parent_sampled_short_circuit/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+556.120%; -555.916%]

scenario:glob_matcher/ascii_case_insensitive_match/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+590.086%; -572.186%]

scenario:glob_matcher/ascii_exact_match/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+565.612%; -560.409%]

scenario:glob_matcher/ascii_exact_miss/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+559.509%; -557.515%]

scenario:glob_matcher/ascii_wildcard_backtrack_match/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+558.084%; -556.842%]

scenario:glob_matcher/ascii_wildcard_heavy_backtrack/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+555.735%; -555.735%]

scenario:glob_matcher/ascii_wildcard_question_match/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+553.410%; -554.642%]

scenario:glob_matcher/ascii_wildcard_star_match/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+559.662%; -557.587%]

scenario:glob_matcher/star_short_circuit/allocated_bytes

  • unstable execution_time [-0.000ns; +0.000ns] or [+554.871%; -555.328%]

Candidate

Omitted due to size.

Baseline

Omitted due to size.

@datadog-prod-us1-5

datadog-prod-us1-5 Bot commented Oct 2, 2026 •
edited by datadog-datadog-prod-us1-2 Bot
Loading

Copy link
Copy Markdown

Tests

⚠️ Warnings

Your PR has warnings. Please review the issues below.

❄️ 2 New flaky tests detected

service::sender::ffe_submission_tests::ffe_pending_configuration_precedes_observation_after_backpressure from datadog-sidecar 
thread 'service::sender::ffe_submission_tests::ffe_pending_configuration_precedes_observation_after_backpressure' panicked at datadog-sidecar/src/service/sender/ffe_submission_tests.rs:164:34

thread 'service::sender::ffe_submission_tests::ffe_pending_configuration_precedes_observation_after_backpressure' panicked at datadog-sidecar/src/service/sender/ffe_submission_tests.rs:164:34:
priority before copy
note: run with \`RUST_BACKTRACE=1\` environment variable to display a backtrace
service::sender::ffe_submission_tests::ffe_post_check_backpressure_drops_without_closing_connection from datadog-sidecar 
thread 'service::sender::ffe_submission_tests::ffe_post_check_backpressure_drops_without_closing_connection' panicked at datadog-sidecar/src/service/sender/ffe_submission_tests.rs:185:5

thread 'service::sender::ffe_submission_tests::ffe_post_check_backpressure_drops_without_closing_connection' panicked at datadog-sidecar/src/service/sender/ffe_submission_tests.rs:185:5:
assertion \`left == right\` failed
  left: Accepted
 right: WouldBlock
note: run with \`RUST_BACKTRACE=1\` environment variable to display a backtrace

View in Flaky Test Management

ℹ️ Info

No other issues found (see more)

🧪 All tests passed

🎯 Code Coverage (details)
• Patch Coverage: 97.14%
• Overall Coverage: 80.69% (+0.16%)

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: a142ab6 | Docs | View more details | Give us feedback!

@dd-octo-sts

dd-octo-sts Bot commented Oct 2, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Artifact Size Benchmark Report

aarch64-alpine-linux-musl
Artifact Baseline Commit Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a 96.62 MB 96.62 MB -0% (-40 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so 9.08 MB 9.08 MB 0% (0 B) 👌
aarch64-unknown-linux-gnu
Artifact Baseline Commit Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a 107.94 MB 107.94 MB -0% (-160 B) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so 12.27 MB 12.27 MB +0% (+8 B) 👌
libdatadog-x64-windows
Artifact Baseline Commit Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll 29.08 MB 29.08 MB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib 97.94 KB 97.94 KB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb 191.78 MB 191.78 MB 0% (0 B) 👌
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib 819.94 MB 819.67 MB --.03% (-277.15 KB) 💪
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll 9.76 MB 9.76 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib 97.94 KB 97.94 KB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb 27.62 MB 27.62 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib 55.82 MB 55.82 MB +0% (+48 B) 👌
libdatadog-x86-windows
Artifact Baseline Commit Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll 25.51 MB 25.51 MB +0% (+512 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib 99.47 KB 99.47 KB 0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb 197.51 MB 197.51 MB 0% (0 B) 👌
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib 801.93 MB 801.91 MB -0% (-14.47 KB) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll 7.58 MB 7.58 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib 99.47 KB 99.47 KB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb 29.73 MB 29.73 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib 52.73 MB 52.73 MB -0% (-180 B) 👌
x86_64-alpine-linux-musl
Artifact Baseline Commit Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a 86.47 MB 86.47 MB +0% (+192 B) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so 10.10 MB 10.10 MB 0% (0 B) 👌
x86_64-unknown-linux-gnu
Artifact Baseline Commit Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a 102.39 MB 102.38 MB -0% (-1.53 KB) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so 12.35 MB 12.35 MB 0% (0 B) 👌

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

ci-build sidecar

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@vjfridge