Skip to content

fix(ffe): require explicit allocation doLog values - #2705

Draft
leoromanovsky wants to merge 1 commit into
mainfrom
leoromanovsky/dolog-required
Draft

leoromanovsky wants to merge 1 commit into
mainfrom
leoromanovsky/dolog-required

Conversation

@leoromanovsky

Copy link
Copy Markdown
Contributor

What does this PR do?

Require an explicit boolean doLog in every UFC allocation. Missing, null, and incorrectly typed values reject the affected flag with PARSE_ERROR. Other flags remain usable. Explicit true and false retain their behavior.

Motivation

The UFC schema requires doLog, but the Rust decoder currently defaults an omitted value to true. This silently enables exposure logging for malformed configuration.

Additional Notes

Pins the shared cases from DataDog/ffe-system-test-data#51. Python, Ruby, and PHP must consume a libdatadog release or dependency revision containing this change.

How to test the change?

Parser tests and 321 shared fixture cases cover valid booleans, omission, null, wrong types, invalid allocations before and after a match, and valid neighboring flags. The existing FFI test checks ERROR / PARSE_ERROR propagation. The native suites pass: 94 tests, none skipped.

Consumer system tests are not completed for 096a3cc012cb895a23a6738e1df480c7201193e7. Native tests do not prove Python, Ruby, or PHP runtime integration.

@github-actions

Copy link
Copy Markdown
Contributor

📚 Documentation Check Results

⚠️ 391 documentation warning(s) found

📦 libdd-ffe-test-suite - ✅ No warnings

📦 libdd-ffe - 391 warning(s)


Updated: 2026-10-20 20:01:42 UTC | Commit: fee3b10 | missing-docs job results

@github-actions

Copy link
Copy Markdown
Contributor

🔒 Cargo Deny Results

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

📦 libdd-ffe-test-suite - 6 error(s)

Show output
info: syncing channel updates for 1.87.0-x86_64-unknown-linux-gnu
info: latest update on 2025-05-15 for version 1.87.0 (17067e9ac 2025-05-09)
info: downloading 6 components
warn: the missing active toolchain `1.87.0-x86_64-unknown-linux-gnu` has been auto-installed
warn: this might cause rustup commands to take longer time to finish than expected
info: you may opt out with `RUSTUP_AUTO_INSTALL=0` or `rustup set auto-install disable`
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
     └── (dev) libdd-ffe v2.0.0
         └── (dev) libdd-ffe-test-suite v46.0.0

error[vulnerability]: TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:194:1
    │
194 │ 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/pull/3265
    ├ 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
      │       │   ├── (dev) libdd-ffe v2.0.0
      │       │   │   └── (dev) libdd-ffe-test-suite v46.0.0
      │       │   └── libdd-remote-config v7.0.0
      │       │       ├── libdd-ffe v2.0.0 (*)
      │       │       └── (dev) libdd-remote-config v7.0.0 (*)
      │       ├── libdd-ffe v2.0.0 (*)
      │       └── libdd-remote-config v7.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 (*)

error[vulnerability]: `Debug` impls for client session values expose TLS secrets
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:194:1
    │
194 │ rustls 0.23.37 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0346
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0346
    ├ The `Debug` implementations of `Tls12ClientSessionValue` and
      `Tls13ClientSessionValue` were derived, and so included the TLS 1.2 master
      secret or TLS 1.3 resumption PSK in their output.
      
      Custom `ClientSessionStore` implementations that format these values with
      `Debug` (for example, when logging) could disclose these secrets to readers of
      the logs. This conflicts with rustls's
      [key-material redaction policy](https://github.com/rustls/rustls/blob/99f2358cae2954837dbb866faf6727de75489ab9/SECURITY.md#boundary-public-api).
      
      Ordinary connection and built-in session cache `Debug` output is redacted and
      is not affected.
    ├ Announcement: https://github.com/rustls/rustls/pull/3299
    ├ Solution: Upgrade to >=0.23.46 (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
      │       │   ├── (dev) libdd-ffe v2.0.0
      │       │   │   └── (dev) libdd-ffe-test-suite v46.0.0
      │       │   └── libdd-remote-config v7.0.0
      │       │       ├── libdd-ffe v2.0.0 (*)
      │       │       └── (dev) libdd-remote-config v7.0.0 (*)
      │       ├── libdd-ffe v2.0.0 (*)
      │       └── libdd-remote-config v7.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 (*)

error[vulnerability]: Brotli certificate decompression can allocate up to 1 GiB before authentication
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:194:1
    │
194 │ rustls 0.23.37 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0348
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0348
    ├ The built-in Brotli certificate decompressor (enabled by the non-default
      `brotli` crate feature) bounded the size of the decompressed output, but
      accepted a peer-selected history window. Brotli's large-window extension was
      enabled, so a five-byte header could cause an allocation of 1 GiB. A peer can
      abort a process whose allocator cannot satisfy that request.
      
      No trusted certificate is required by the attacker. Affected configurations are:
      
      - clients that enable the `brotli` feature and connect to a malicious server, and
      - servers that enable the `brotli` feature and request client certificates.
      
      Applications that do not enable the `brotli` feature are not affected.
    ├ Announcement: https://github.com/rustls/rustls/pull/3297
    ├ Solution: Upgrade to >=0.23.46 (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
      │       │   ├── (dev) libdd-ffe v2.0.0
      │       │   │   └── (dev) libdd-ffe-test-suite v46.0.0
      │       │   └── libdd-remote-config v7.0.0
      │       │       ├── libdd-ffe v2.0.0 (*)
      │       │       └── (dev) libdd-remote-config v7.0.0 (*)
      │       ├── libdd-ffe v2.0.0 (*)
      │       └── libdd-remote-config v7.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 (*)

error[vulnerability]: Unauthenticated ServerHello can downgrade later connections to classical key exchange
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:194:1
    │
194 │ rustls 0.23.37 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0349
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0349
    ├ The client recorded the server-selected key exchange group for each server
      name when processing the ServerHello, before the server was authenticated.
      This record is used to predict which key share to send in future ClientHellos
      to that server name.
      
      A network attacker can answer one connection attempt with a ServerHello
      selecting X25519, and then close the connection. Later ClientHellos for that
      name carry only an X25519 key share, while `supported_groups` still lists
      X25519MLKEM768 first. If the genuine server accepts that share rather than
      sending a HelloRetryRequest for its preferred hybrid group, the handshake
      completes with classical-only key exchange and no error. This persists for as
      long as the entry stays in the client's session store.
      
      The impact is loss of post-quantum confidentiality for affected connections
      ("harvest now, decrypt later"). There is no key compromise and no
      authentication bypass.
      
      The following are not affected:
      
      - connections to servers which send a HelloRetryRequest for their preferred group,
      - clients with resumption disabled (as nothing is stored), and
      - other server names.
      
      This behaviour is discussed in
      [draft-ietf-tls-key-share-prediction](https://www.ietf.org/archive/id/draft-ietf-tls-key-share-prediction-01.html#name-security-considerations),
      so the practical impact depends largely on server policy.
    ├ Announcement: https://github.com/rustls/rustls/pull/3355
    ├ Solution: Upgrade to >=0.23.46 (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
      │       │   ├── (dev) libdd-ffe v2.0.0
      │       │   │   └── (dev) libdd-ffe-test-suite v46.0.0
      │       │   └── libdd-remote-config v7.0.0
      │       │       ├── libdd-ffe v2.0.0 (*)
      │       │       └── (dev) libdd-remote-config v7.0.0 (*)
      │       ├── libdd-ffe v2.0.0 (*)
      │       └── libdd-remote-config v7.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 (*)

error[vulnerability]: Certificate verification may accept distrusted intermediates
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:199:1
    │
199 │ rustls-webpki 0.103.13 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0382
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0382
    ├ Affected versions may accept certificate paths containing distrusted emSign
      intermediate public keys when the configured trust anchors allow such paths.
      The private keys corresponding to these intermediates are now well known.
      
      Versions 0.103.16 and 0.104.0-alpha.8 reject paths containing these public keys.
    ├ Announcement: https://github.com/rustls/webpki/pull/546
    ├ Solution: Upgrade to >=0.103.16, <0.104.0-alpha.1 OR >=0.104.0-alpha.8 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.13
      ├── rustls v0.23.37
      │   ├── hyper-rustls v0.27.7
      │   │   └── libdd-common v8.0.0
      │   │       ├── libdd-capabilities-impl v7.0.0
      │   │       │   ├── (dev) libdd-ffe v2.0.0
      │   │       │   │   └── (dev) libdd-ffe-test-suite v46.0.0
      │   │       │   └── libdd-remote-config v7.0.0
      │   │       │       ├── libdd-ffe v2.0.0 (*)
      │   │       │       └── (dev) libdd-remote-config v7.0.0 (*)
      │   │       ├── libdd-ffe v2.0.0 (*)
      │   │       └── libdd-remote-config v7.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 (*)
      └── rustls-platform-verifier v0.6.2 (*)

advisories FAILED, bans ok, sources ok

📦 libdd-ffe - 7 error(s)

Show output
error[unmaintained]: Bincode is unmaintained
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:22:1
   │
22 │ 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
     └── (dev) libdd-ffe v2.0.0

error[unsound]: Potential use-after-free due to lack of panic safety in `LruCache::pop()`
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:128:1
    │
128 │ 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

error[vulnerability]: TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:170:1
    │
170 │ 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/pull/3265
    ├ 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
      │       │   ├── (dev) libdd-ffe v2.0.0
      │       │   └── libdd-remote-config v7.0.0
      │       │       ├── libdd-ffe v2.0.0 (*)
      │       │       └── (dev) libdd-remote-config v7.0.0 (*)
      │       ├── libdd-ffe v2.0.0 (*)
      │       └── libdd-remote-config v7.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 (*)

error[vulnerability]: `Debug` impls for client session values expose TLS secrets
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:170:1
    │
170 │ rustls 0.23.37 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0346
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0346
    ├ The `Debug` implementations of `Tls12ClientSessionValue` and
      `Tls13ClientSessionValue` were derived, and so included the TLS 1.2 master
      secret or TLS 1.3 resumption PSK in their output.
      
      Custom `ClientSessionStore` implementations that format these values with
      `Debug` (for example, when logging) could disclose these secrets to readers of
      the logs. This conflicts with rustls's
      [key-material redaction policy](https://github.com/rustls/rustls/blob/99f2358cae2954837dbb866faf6727de75489ab9/SECURITY.md#boundary-public-api).
      
      Ordinary connection and built-in session cache `Debug` output is redacted and
      is not affected.
    ├ Announcement: https://github.com/rustls/rustls/pull/3299
    ├ Solution: Upgrade to >=0.23.46 (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
      │       │   ├── (dev) libdd-ffe v2.0.0
      │       │   └── libdd-remote-config v7.0.0
      │       │       ├── libdd-ffe v2.0.0 (*)
      │       │       └── (dev) libdd-remote-config v7.0.0 (*)
      │       ├── libdd-ffe v2.0.0 (*)
      │       └── libdd-remote-config v7.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 (*)

error[vulnerability]: Brotli certificate decompression can allocate up to 1 GiB before authentication
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:170:1
    │
170 │ rustls 0.23.37 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0348
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0348
    ├ The built-in Brotli certificate decompressor (enabled by the non-default
      `brotli` crate feature) bounded the size of the decompressed output, but
      accepted a peer-selected history window. Brotli's large-window extension was
      enabled, so a five-byte header could cause an allocation of 1 GiB. A peer can
      abort a process whose allocator cannot satisfy that request.
      
      No trusted certificate is required by the attacker. Affected configurations are:
      
      - clients that enable the `brotli` feature and connect to a malicious server, and
      - servers that enable the `brotli` feature and request client certificates.
      
      Applications that do not enable the `brotli` feature are not affected.
    ├ Announcement: https://github.com/rustls/rustls/pull/3297
    ├ Solution: Upgrade to >=0.23.46 (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
      │       │   ├── (dev) libdd-ffe v2.0.0
      │       │   └── libdd-remote-config v7.0.0
      │       │       ├── libdd-ffe v2.0.0 (*)
      │       │       └── (dev) libdd-remote-config v7.0.0 (*)
      │       ├── libdd-ffe v2.0.0 (*)
      │       └── libdd-remote-config v7.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 (*)

error[vulnerability]: Unauthenticated ServerHello can downgrade later connections to classical key exchange
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:170:1
    │
170 │ rustls 0.23.37 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0349
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0349
    ├ The client recorded the server-selected key exchange group for each server
      name when processing the ServerHello, before the server was authenticated.
      This record is used to predict which key share to send in future ClientHellos
      to that server name.
      
      A network attacker can answer one connection attempt with a ServerHello
      selecting X25519, and then close the connection. Later ClientHellos for that
      name carry only an X25519 key share, while `supported_groups` still lists
      X25519MLKEM768 first. If the genuine server accepts that share rather than
      sending a HelloRetryRequest for its preferred hybrid group, the handshake
      completes with classical-only key exchange and no error. This persists for as
      long as the entry stays in the client's session store.
      
      The impact is loss of post-quantum confidentiality for affected connections
      ("harvest now, decrypt later"). There is no key compromise and no
      authentication bypass.
      
      The following are not affected:
      
      - connections to servers which send a HelloRetryRequest for their preferred group,
      - clients with resumption disabled (as nothing is stored), and
      - other server names.
      
      This behaviour is discussed in
      [draft-ietf-tls-key-share-prediction](https://www.ietf.org/archive/id/draft-ietf-tls-key-share-prediction-01.html#name-security-considerations),
      so the practical impact depends largely on server policy.
    ├ Announcement: https://github.com/rustls/rustls/pull/3355
    ├ Solution: Upgrade to >=0.23.46 (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
      │       │   ├── (dev) libdd-ffe v2.0.0
      │       │   └── libdd-remote-config v7.0.0
      │       │       ├── libdd-ffe v2.0.0 (*)
      │       │       └── (dev) libdd-remote-config v7.0.0 (*)
      │       ├── libdd-ffe v2.0.0 (*)
      │       └── libdd-remote-config v7.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 (*)

error[vulnerability]: Certificate verification may accept distrusted intermediates
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:175:1
    │
175 │ rustls-webpki 0.103.13 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0382
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0382
    ├ Affected versions may accept certificate paths containing distrusted emSign
      intermediate public keys when the configured trust anchors allow such paths.
      The private keys corresponding to these intermediates are now well known.
      
      Versions 0.103.16 and 0.104.0-alpha.8 reject paths containing these public keys.
    ├ Announcement: https://github.com/rustls/webpki/pull/546
    ├ Solution: Upgrade to >=0.103.16, <0.104.0-alpha.1 OR >=0.104.0-alpha.8 (try `cargo update -p rustls-webpki`)
    ├ rustls-webpki v0.103.13
      ├── rustls v0.23.37
      │   ├── hyper-rustls v0.27.7
      │   │   └── libdd-common v8.0.0
      │   │       ├── libdd-capabilities-impl v7.0.0
      │   │       │   ├── (dev) libdd-ffe v2.0.0
      │   │       │   └── libdd-remote-config v7.0.0
      │   │       │       ├── libdd-ffe v2.0.0 (*)
      │   │       │       └── (dev) libdd-remote-config v7.0.0 (*)
      │   │       ├── libdd-ffe v2.0.0 (*)
      │   │       └── libdd-remote-config v7.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 (*)
      └── rustls-platform-verifier v0.6.2 (*)

advisories FAILED, bans ok, sources ok

Updated: 2026-10-20 20:03:29 UTC | Commit: fee3b10 | dependency-check job results

@datadog-datadog-prod-us1-2

datadog-datadog-prod-us1-2 Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

Tests

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 77.56% (-4.66%)

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

@pr-commenter

pr-commenter Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

Benchmarks

Comparison

Benchmark execution time: 2026-10-20 20:10:28

Comparing candidate commit 096a3cc in PR branch leoromanovsky/dolog-required with baseline commit ce77b3f in branch main.

📊 Benchmarking dashboard

Found 0 performance improvements and 4 performance regressions! Performance is the same for 10 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:flagevaluation_evp/coalescer/stress/10flags_1000users_250fields

  • 🟥 execution_time [+14.322ms; +14.927ms] or [+7.633%; +7.955%]
  • 🟥 throughput [-393.410op/s; -377.546op/s] or [-7.382%; -7.084%]

scenario:flagevaluation_evp/payloads/stress/10flags_1000users_250fields

  • 🟥 execution_time [+15.997ms; +16.156ms] or [+8.962%; +9.052%]
  • 🟥 throughput [-465.222op/s; -460.655op/s] or [-8.304%; -8.222%]

Candidate

Candidate benchmark details

Group 1

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz 096a3cc 1792526314 leoromanovsky/dolog-required
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
flagevaluation_evp/payloads/scale/2500flags_500users_20fields execution_time 34.661ms 35.072ms ± 0.141ms 35.092ms ± 0.088ms 35.170ms 35.274ms 35.380ms 35.465ms 1.06% -0.345 0.200 0.40% 0.010ms 1 200
flagevaluation_evp/payloads/scale/2500flags_500users_20fields throughput 70492.998op/s 71283.416op/s ± 287.347op/s 71240.499op/s ± 177.951op/s 71465.939op/s 71817.254op/s 72034.862op/s 72127.287op/s 1.24% 0.370 0.214 0.40% 20.319op/s 1 200
flagevaluation_evp/payloads/stress/10flags_1000users_250fields execution_time 193.451ms 194.562ms ± 0.427ms 194.547ms ± 0.230ms 194.777ms 195.105ms 195.584ms 197.904ms 1.73% 2.448 17.885 0.22% 0.030ms 1 200
flagevaluation_evp/payloads/stress/10flags_1000users_250fields throughput 5052.966op/s 5139.783op/s ± 11.227op/s 5140.148op/s ± 6.067op/s 5146.127op/s 5155.516op/s 5159.903op/s 5169.263op/s 0.57% -2.358 17.066 0.22% 0.794op/s 1 200
flagevaluation_evp/payloads/typical/100flags_50users_10fields execution_time 842.872µs 844.718µs ± 0.665µs 844.699µs ± 0.391µs 845.100µs 845.869µs 846.514µs 848.093µs 0.40% 0.826 3.135 0.08% 0.047µs 1 200
flagevaluation_evp/payloads/typical/100flags_50users_10fields throughput 117911.551op/s 118382.721op/s ± 93.109op/s 118385.429op/s ± 54.816op/s 118438.896op/s 118515.335op/s 118581.002op/s 118642.019op/s 0.22% -0.815 3.096 0.08% 6.584op/s 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
flagevaluation_evp/payloads/scale/2500flags_500users_20fields execution_time [35.052ms; 35.091ms] or [-0.056%; +0.056%] None None None
flagevaluation_evp/payloads/scale/2500flags_500users_20fields throughput [71243.593op/s; 71323.240op/s] or [-0.056%; +0.056%] None None None
flagevaluation_evp/payloads/stress/10flags_1000users_250fields execution_time [194.502ms; 194.621ms] or [-0.030%; +0.030%] None None None
flagevaluation_evp/payloads/stress/10flags_1000users_250fields throughput [5138.227op/s; 5141.339op/s] or [-0.030%; +0.030%] None None None
flagevaluation_evp/payloads/typical/100flags_50users_10fields execution_time [844.626µs; 844.811µs] or [-0.011%; +0.011%] None None None
flagevaluation_evp/payloads/typical/100flags_50users_10fields throughput [118369.817op/s; 118395.626op/s] or [-0.011%; +0.011%] None None None

Group 2

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz 096a3cc 1792526314 leoromanovsky/dolog-required
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
sdk_test_data/rules-based execution_time 261.661µs 269.176µs ± 12.757µs 264.944µs ± 1.454µs 268.550µs 286.258µs 310.903µs 391.412µs 47.73% 5.750 45.334 4.73% 0.902µs 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
sdk_test_data/rules-based execution_time [267.408µs; 270.944µs] or [-0.657%; +0.657%] None None None

Group 3

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz 096a3cc 1792526314 leoromanovsky/dolog-required
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
single_flag_killswitch/rules-based execution_time 156.630ns 160.699ns ± 2.880ns 160.234ns ± 1.438ns 161.718ns 165.224ns 168.958ns 179.666ns 12.13% 2.347 10.403 1.79% 0.204ns 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
single_flag_killswitch/rules-based execution_time [160.300ns; 161.098ns] or [-0.248%; +0.248%] None None None

Group 4

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz 096a3cc 1792526314 leoromanovsky/dolog-required
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
flagevaluation_evp/coalescer/scale/2500flags_500users_20fields execution_time 31.551ms 31.712ms ± 0.075ms 31.721ms ± 0.052ms 31.758ms 31.825ms 31.928ms 31.949ms 0.72% 0.276 0.235 0.24% 0.005ms 1 200
flagevaluation_evp/coalescer/scale/2500flags_500users_20fields throughput 78248.601op/s 78835.633op/s ± 186.038op/s 78811.592op/s ± 127.981op/s 78977.312op/s 79122.574op/s 79216.484op/s 79236.013op/s 0.54% -0.261 0.210 0.24% 13.155op/s 1 200
flagevaluation_evp/coalescer/stress/10flags_1000users_250fields execution_time 201.272ms 202.269ms ± 1.423ms 201.855ms ± 0.185ms 202.056ms 206.976ms 207.452ms 207.530ms 2.81% 3.049 7.759 0.70% 0.101ms 1 200
flagevaluation_evp/coalescer/stress/10flags_1000users_250fields throughput 4818.576op/s 4944.143op/s ± 34.059op/s 4954.054op/s ± 4.539op/s 4958.050op/s 4962.325op/s 4965.800op/s 4968.389op/s 0.29% -3.039 7.716 0.69% 2.408op/s 1 200
flagevaluation_evp/coalescer/typical/100flags_50users_10fields execution_time 695.461µs 697.394µs ± 1.110µs 697.377µs ± 0.466µs 697.802µs 698.417µs 698.792µs 709.884µs 1.79% 7.062 78.217 0.16% 0.079µs 1 200
flagevaluation_evp/coalescer/typical/100flags_50users_10fields throughput 140868.102op/s 143391.284op/s ± 225.801op/s 143394.421op/s ± 95.874op/s 143499.885op/s 143629.231op/s 143761.164op/s 143789.557op/s 0.28% -6.919 76.138 0.16% 15.967op/s 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
flagevaluation_evp/coalescer/scale/2500flags_500users_20fields execution_time [31.701ms; 31.722ms] or [-0.033%; +0.033%] None None None
flagevaluation_evp/coalescer/scale/2500flags_500users_20fields throughput [78809.850op/s; 78861.417op/s] or [-0.033%; +0.033%] None None None
flagevaluation_evp/coalescer/stress/10flags_1000users_250fields execution_time [202.072ms; 202.467ms] or [-0.098%; +0.098%] None None None
flagevaluation_evp/coalescer/stress/10flags_1000users_250fields throughput [4939.422op/s; 4948.863op/s] or [-0.095%; +0.095%] None None None
flagevaluation_evp/coalescer/typical/100flags_50users_10fields execution_time [697.240µs; 697.548µs] or [-0.022%; +0.022%] None None None
flagevaluation_evp/coalescer/typical/100flags_50users_10fields throughput [143359.990op/s; 143422.578op/s] or [-0.022%; +0.022%] None None None

Baseline

Baseline benchmark details

Group 1

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz ce77b3f 1792519980 main
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
flagevaluation_evp/payloads/scale/2500flags_500users_20fields execution_time 33.683ms 34.473ms ± 0.228ms 34.480ms ± 0.160ms 34.636ms 34.809ms 34.945ms 35.098ms 1.79% -0.252 0.137 0.66% 0.016ms 1 200
flagevaluation_evp/payloads/scale/2500flags_500users_20fields throughput 71228.933op/s 72523.634op/s ± 480.907op/s 72506.040op/s ± 334.655op/s 72865.688op/s 73333.319op/s 73692.041op/s 74221.569op/s 2.37% 0.293 0.186 0.66% 34.005op/s 1 200
flagevaluation_evp/payloads/stress/10flags_1000users_250fields execution_time 177.440ms 178.486ms ± 0.384ms 178.471ms ± 0.236ms 178.728ms 179.113ms 179.448ms 179.606ms 0.64% 0.133 0.127 0.21% 0.027ms 1 200
flagevaluation_evp/payloads/stress/10flags_1000users_250fields throughput 5567.744op/s 5602.721op/s ± 12.062op/s 5603.148op/s ± 7.398op/s 5610.250op/s 5621.745op/s 5628.227op/s 5635.708op/s 0.58% -0.120 0.121 0.21% 0.853op/s 1 200
flagevaluation_evp/payloads/typical/100flags_50users_10fields execution_time 828.643µs 831.299µs ± 1.205µs 831.215µs ± 0.701µs 831.941µs 833.490µs 834.504µs 834.692µs 0.42% 0.353 0.016 0.14% 0.085µs 1 200
flagevaluation_evp/payloads/typical/100flags_50users_10fields throughput 119804.675op/s 120293.920op/s ± 174.299op/s 120305.837op/s ± 101.465op/s 120404.969op/s 120561.244op/s 120629.746op/s 120679.178op/s 0.31% -0.345 0.007 0.14% 12.325op/s 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
flagevaluation_evp/payloads/scale/2500flags_500users_20fields execution_time [34.441ms; 34.505ms] or [-0.092%; +0.092%] None None None
flagevaluation_evp/payloads/scale/2500flags_500users_20fields throughput [72456.985op/s; 72590.283op/s] or [-0.092%; +0.092%] None None None
flagevaluation_evp/payloads/stress/10flags_1000users_250fields execution_time [178.432ms; 178.539ms] or [-0.030%; +0.030%] None None None
flagevaluation_evp/payloads/stress/10flags_1000users_250fields throughput [5601.050op/s; 5604.393op/s] or [-0.030%; +0.030%] None None None
flagevaluation_evp/payloads/typical/100flags_50users_10fields execution_time [831.132µs; 831.466µs] or [-0.020%; +0.020%] None None None
flagevaluation_evp/payloads/typical/100flags_50users_10fields throughput [120269.764op/s; 120318.076op/s] or [-0.020%; +0.020%] None None None

Group 2

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz ce77b3f 1792519980 main
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
sdk_test_data/rules-based execution_time 256.649µs 263.442µs ± 12.248µs 260.518µs ± 1.512µs 262.664µs 273.975µs 317.730µs 390.233µs 49.79% 7.085 62.002 4.64% 0.866µs 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
sdk_test_data/rules-based execution_time [261.745µs; 265.140µs] or [-0.644%; +0.644%] None None None

Group 3

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz ce77b3f 1792519980 main
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
single_flag_killswitch/rules-based execution_time 155.558ns 159.537ns ± 2.752ns 159.115ns ± 1.575ns 160.710ns 164.351ns 167.587ns 171.544ns 7.81% 1.327 2.332 1.72% 0.195ns 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
single_flag_killswitch/rules-based execution_time [159.155ns; 159.918ns] or [-0.239%; +0.239%] None None None

Group 4

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz ce77b3f 1792519980 main
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
flagevaluation_evp/coalescer/scale/2500flags_500users_20fields execution_time 30.695ms 30.924ms ± 0.067ms 30.924ms ± 0.039ms 30.966ms 31.022ms 31.106ms 31.117ms 0.62% -0.239 1.130 0.22% 0.005ms 1 200
flagevaluation_evp/coalescer/scale/2500flags_500users_20fields throughput 80341.212op/s 80842.454op/s ± 176.225op/s 80843.123op/s ± 101.420op/s 80936.048op/s 81156.965op/s 81363.268op/s 81446.896op/s 0.75% 0.259 1.143 0.22% 12.461op/s 1 200
flagevaluation_evp/coalescer/stress/10flags_1000users_250fields execution_time 186.400ms 187.645ms ± 1.653ms 187.059ms ± 0.216ms 187.344ms 192.326ms 192.516ms 192.660ms 2.99% 2.352 3.839 0.88% 0.117ms 1 200
flagevaluation_evp/coalescer/stress/10flags_1000users_250fields throughput 5190.484op/s 5329.620op/s ± 45.996op/s 5345.904op/s ± 6.169op/s 5350.392op/s 5356.682op/s 5362.090op/s 5364.820op/s 0.35% -2.344 3.813 0.86% 3.252op/s 1 200
flagevaluation_evp/coalescer/typical/100flags_50users_10fields execution_time 690.044µs 691.826µs ± 0.848µs 691.720µs ± 0.611µs 692.417µs 693.379µs 693.935µs 694.441µs 0.39% 0.479 -0.135 0.12% 0.060µs 1 200
flagevaluation_evp/coalescer/typical/100flags_50users_10fields throughput 144000.803op/s 144545.132op/s ± 177.150op/s 144567.130op/s ± 127.602op/s 144676.564op/s 144790.160op/s 144869.799op/s 144918.325op/s 0.24% -0.473 -0.144 0.12% 12.526op/s 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
flagevaluation_evp/coalescer/scale/2500flags_500users_20fields execution_time [30.915ms; 30.934ms] or [-0.030%; +0.030%] None None None
flagevaluation_evp/coalescer/scale/2500flags_500users_20fields throughput [80818.031op/s; 80866.877op/s] or [-0.030%; +0.030%] None None None
flagevaluation_evp/coalescer/stress/10flags_1000users_250fields execution_time [187.416ms; 187.874ms] or [-0.122%; +0.122%] None None None
flagevaluation_evp/coalescer/stress/10flags_1000users_250fields throughput [5323.246op/s; 5335.995op/s] or [-0.120%; +0.120%] None None None
flagevaluation_evp/coalescer/typical/100flags_50users_10fields execution_time [691.709µs; 691.944µs] or [-0.017%; +0.017%] None None None
flagevaluation_evp/coalescer/typical/100flags_50users_10fields throughput [144520.581op/s; 144569.684op/s] or [-0.017%; +0.017%] None None None

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant