fix(data-pipeline): contain panics in combined FFI by lloeki · Pull Request #2302 · DataDog/libdatadog

lloeki · 2026-07-30T11:02:37Z

AI-generated code disclosure: this PR was implemented with substantial AI assistance and manually reviewed and validated.

What does this PR do?

Ensures the combined libdatadog profiling artifact enables catch_panic for data-pipeline FFI entry points. It also adds a packaged C regression that triggers capacity overflow and verifies that the FFI returns an error instead of aborting the process.

Motivation

The standalone data-pipeline FFI crate enables panic containment by default, but the combined profiling artifact disables dependency defaults and did not re-enable it. This closes APMSP-3830 before the native trace exporter payload APIs ship together.

Additional Notes

Stack position: L0, current PR: DataDog/libdatadog PR 2302.

These open L0-L5 changes are not included in libdatadog v38.0.0. They are planned to ship together in a single libdatadog v39 release, with the common dd-trace-rb uptake tracked by R3 DataDog/dd-trace-rb PR 6143.

Complete expected libdatadog review and merge order for that single v39 release:

Level	libdatadog PR	Matching dd-trace-rb consumer
L0 (current)	DataDog/libdatadog PR 2302	Release prerequisite; no payload API consumer
L1	DataDog/libdatadog PR 2303	R4 DataDog/dd-trace-rb PR 6130
L2	DataDog/libdatadog PR 2305	R5 DataDog/dd-trace-rb PR 6129
L3	DataDog/libdatadog PR 2301	R6 DataDog/dd-trace-rb PR 6134
L4	DataDog/libdatadog PR 2304	R7 DataDog/dd-trace-rb PR 6132
L5	DataDog/libdatadog PR 2300	R8 DataDog/dd-trace-rb PR 6133

L0-L3 are independent and can be reviewed in parallel. Merging them in the listed order is still recommended because it reduces integration and release-branch conflicts, and lands panic containment before the new payload surfaces. L4 is stacked on L1, and L5 is stacked on L4.

The matching payload consumers are R4 DataDog/dd-trace-rb PR 6130, R5 DataDog/dd-trace-rb PR 6129, R6 DataDog/dd-trace-rb PR 6134, R7 DataDog/dd-trace-rb PR 6132, and R8 DataDog/dd-trace-rb PR 6133. All depend through the common v39 uptake in R3 DataDog/dd-trace-rb PR 6143. The downstream review and merge order after R3 is R4, R5, R6, R7, then R8; R7 also depends on R4, and R8 depends on R7.

DataDog/libdatadog-rb v37 PR 65 and DataDog/libdatadog-rb v38 PR 66 are separate ordered prerequisite releases only for R2 DataDog/dd-trace-rb PR 6131 and its ForkSafeRuntime uptake. They do not contain the open L0-L5 changes or payload APIs. R3 is stacked on R2, but R3, rather than either prerequisite package, is the common v39 payload-API uptake.

L0 tracks APMSP-3830; L1-L5 implement the payload work tracked by APMSP-3219.

How to test the change?

Prior local validation completed successfully:

nix develop -c cargo test -p libdd-profiling-ffi --features data-pipeline-ffi passed the combined profiling/data-pipeline FFI suite: 57 tests.
nix develop -c cargo test -p libdd-data-pipeline-ffi --features catch_panic trace_chunks_new_with_overflow_capacity_returns_panic_error passed.
nix develop -c cargo test -p libdd-data-pipeline-ffi --features catch_panic begin_chunk_with_overflow_capacity_returns_panic_error passed.
nix develop -c cargo ffi-test --filter trace_exporter_panic_containment built and passed the packaged C panic-containment regression.
nix develop .#nightly --command cargo fmt --all -- --check passed.
nix develop -c cargo clippy -p libdd-profiling-ffi --all-targets --features data-pipeline-ffi -- -D warnings passed.

pr-commenter · 2026-07-30T11:11:11Z

Benchmarks

Comparison

Candidate

Candidate benchmark details

Baseline

Baseline benchmark details

datadog-datadog-us1-prod · 2026-07-30T11:16:12Z

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 91.00%
• Overall Coverage: 75.17% (+0.36%)

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

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

dd-octo-sts · 2026-07-30T11:38:57Z

Artifact Size Benchmark Report

aarch64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so	8.01 MB	8.07 MB	+.80% (+66.32 KB) 🔍
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a	87.32 MB	87.76 MB	+.50% (+452.43 KB) 🔍

aarch64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a	98.55 MB	99.00 MB	+.45% (+461.79 KB) 🔍
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so	10.78 MB	10.88 MB	+.91% (+100.79 KB) 🔍

libdatadog-x64-windows

Artifact	Baseline	Commit	Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll	26.05 MB	26.20 MB	+.60% (+162.50 KB) 🔍
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib	89.60 KB	89.60 KB	0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb	188.07 MB	188.64 MB	+.30% (+584.00 KB) 🔍
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib	980.68 MB	985.22 MB	+.46% (+4.54 MB) 🔍
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll	8.49 MB	8.56 MB	+.84% (+73.50 KB) 🔍
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib	89.60 KB	89.60 KB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb	25.10 MB	25.21 MB	+.43% (+112.00 KB) 🔍
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib	49.92 MB	50.21 MB	+.56% (+291.40 KB) 🔍

libdatadog-x86-windows

Artifact	Baseline	Commit	Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll	22.69 MB	22.84 MB	+.66% (+155.50 KB) 🔍
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib	91.00 KB	91.00 KB	0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb	192.83 MB	193.42 MB	+.30% (+608.00 KB) 🔍
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib	969.32 MB	974.03 MB	+.48% (+4.70 MB) 🔍
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll	6.56 MB	6.61 MB	+.80% (+54.00 KB) 🔍
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib	91.00 KB	91.00 KB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb	26.97 MB	27.11 MB	+.52% (+144.00 KB) 🔍
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib	47.53 MB	47.80 MB	+.56% (+276.70 KB) 🔍

x86_64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a	77.87 MB	78.29 MB	+.54% (+436.83 KB) 🔍
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so	8.93 MB	9.00 MB	+.81% (+74.31 KB) 🔍

x86_64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a	93.36 MB	93.79 MB	+.46% (+441.22 KB) 🔍
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so	10.87 MB	10.97 MB	+.88% (+98.42 KB) 🔍

lloeki · 2026-07-30T11:49:01Z

This is part of the single native trace exporter API release train consumed through DataDog/dd-trace-rb#6131.

Enable `catch_panic` when the data pipeline FFI is bundled through the profiling FFI. Without feature propagation, a Rust panic can cross the combined C library boundary and terminate the host process. Add a packaged C example that triggers a capacity overflow and verifies that the API returns `DDOG_TRACE_EXPORTER_ERROR_CODE_PANIC` instead. APMSP-3830

ekump

LGTM, but you should get another review since I made a couple of commits myself to add a CI check and made a minor change to the example.

lloeki · 2026-08-03T14:23:48Z

I can't self approve but as far as Ruby is concerned, Julio's 7b56f2c LGTM 👍

… panic and that all catch panic enabled crates are in the catch panic list

ekump · 2026-08-03T21:43:51Z

 //!
-//! Expressed as data plus a pure function rather than a wall of `#[cfg]` attributes so
-//! that every combination — including the ones no CI job ever builds — can be asserted
-//! in unit tests (RFC 0016, option E). `builder/src/bin/release.rs` was one of the


I didn't see this RFC

…ontainment

hoolioh · 2026-08-04T08:06:54Z

/merge

gh-worker-devflow-routing-ef8351 · 2026-08-04T08:06:58Z

View all feedbacks in Devflow UI.

2026-08-04 08:06:57 UTC ℹ️ Start processing command /merge

2026-08-04 08:07:02 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in main is approximately 60m (p90).

2026-08-04 08:46:33 UTC ℹ️ MergeQueue: This merge request was merged

AI-generated code disclosure: this PR was implemented with substantial AI assistance and manually reviewed and validated. # What does this PR do? Adds an opaque per-key `meta_struct` blob setter to `TracerSpan`. Keys are validated as UTF-8, while values are copied as uninterpreted binary data. This transitional API lets consumers pass their existing per-key MessagePack blobs without changing the Rust trace model. # Motivation Native exporter consumers cannot currently populate `meta_struct`, which blocks payload parity tracked by [APMSP-3219](https://datadoghq.atlassian.net/browse/APMSP-3219). The opaque setter provides the safe first stage before the language-neutral structured-value APIs. # Additional Notes **Stack position: L1, current PR: [DataDog/libdatadog PR 2303](#2303 These open L0-L5 changes are not included in [libdatadog v38.0.0](https://github.com/DataDog/libdatadog/releases/tag/v38.0.0). They are planned to ship together in a single libdatadog v39 release, with the common dd-trace-rb uptake tracked by [R3 DataDog/dd-trace-rb PR 6143](DataDog/dd-trace-rb#6143). Complete expected libdatadog review and merge order for that single v39 release: | Level | libdatadog PR | Matching dd-trace-rb consumer | | --- | --- | --- | | L0 | [DataDog/libdatadog PR 2302](#2302) | Release prerequisite; no payload API consumer | | **L1 (current)** | **[DataDog/libdatadog PR 2303](#2303 | **[R4 DataDog/dd-trace-rb PR 6130](DataDog/dd-trace-rb#6130 | | L2 | [DataDog/libdatadog PR 2305](#2305) | [R5 DataDog/dd-trace-rb PR 6129](DataDog/dd-trace-rb#6129) | | L3 | [DataDog/libdatadog PR 2301](#2301) | [R6 DataDog/dd-trace-rb PR 6134](DataDog/dd-trace-rb#6134) | | L4 | [DataDog/libdatadog PR 2304](#2304) | [R7 DataDog/dd-trace-rb PR 6132](DataDog/dd-trace-rb#6132) | | L5 | [DataDog/libdatadog PR 2300](#2300) | [R8 DataDog/dd-trace-rb PR 6133](DataDog/dd-trace-rb#6133) | L0-L3 are independent and can be reviewed in parallel. Merging them in the listed order is still recommended because it reduces integration and release-branch conflicts, and lands panic containment before the new payload surfaces. L4 is stacked on L1, and L5 is stacked on L4. The matching payload consumers are [R4 DataDog/dd-trace-rb PR 6130](DataDog/dd-trace-rb#6130), [R5 DataDog/dd-trace-rb PR 6129](DataDog/dd-trace-rb#6129), [R6 DataDog/dd-trace-rb PR 6134](DataDog/dd-trace-rb#6134), [R7 DataDog/dd-trace-rb PR 6132](DataDog/dd-trace-rb#6132), and [R8 DataDog/dd-trace-rb PR 6133](DataDog/dd-trace-rb#6133). All depend through the common v39 uptake in [R3 DataDog/dd-trace-rb PR 6143](DataDog/dd-trace-rb#6143). The downstream review and merge order after R3 is R4, R5, R6, R7, then R8; R7 also depends on R4, and R8 depends on R7. [DataDog/libdatadog-rb v37 PR 65](DataDog/libdatadog-rb#65) and [DataDog/libdatadog-rb v38 PR 66](DataDog/libdatadog-rb#66) are separate ordered prerequisite releases only for [R2 DataDog/dd-trace-rb PR 6131](DataDog/dd-trace-rb#6131) and its `ForkSafeRuntime` uptake. They do not contain the open L0-L5 changes or payload APIs. R3 is stacked on R2, but R3, rather than either prerequisite package, is the common v39 payload-API uptake. L0 tracks [APMSP-3830](https://datadoghq.atlassian.net/browse/APMSP-3830); L1-L5 implement the payload work tracked by [APMSP-3219](https://datadoghq.atlassian.net/browse/APMSP-3219). # How to test the change? Prior local validation completed successfully: - `nix develop -c cargo test -p libdd-data-pipeline-ffi` passed, including arbitrary binary values, overwrite semantics, null handles, and invalid UTF-8 keys. - `nix develop -c cargo clippy -p libdd-data-pipeline-ffi --all-targets -- -D warnings` passed. - `nix develop .#nightly -c cargo fmt --all -- --check` passed. - The generated C header was rebuilt through `nix develop -c cargo run --bin release -- --out /tmp/opencode/native-meta-struct-libdatadog/x86_64-linux` and consumed successfully by the matching dd-trace-rb branch. - `nix develop .#ruby34 --command bundle exec rspec spec/datadog/tracing/transport/native/tracer_span_spec.rb spec/datadog/tracing/transport/native/conformance_spec.rb spec/datadog/tracing/transport/native/transport_spec.rb spec/datadog/appsec/actions_handler/serializable_backtrace_spec.rb` passed 116 examples, including AppSec and AI Guard-shaped wire conformance. - Targeted Standard and Steep checks for the native transport passed. [APMSP-3219]: https://datadoghq.atlassian.net/browse/APMSP-3219?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ [APMSP-3830]: https://datadoghq.atlassian.net/browse/APMSP-3830?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ Co-authored-by: ekump <edmund.kump@datadoghq.com> Co-authored-by: loic.nageleisen <loic.nageleisen@datadoghq.com>

AI-generated code disclosure: this PR was implemented with substantial AI assistance and manually reviewed and validated. # What does this PR do? Adds owned span-event construction and atomic attachment through the data-pipeline FFI. It supports typed scalar attributes, homogeneous typed arrays, empty arrays, event ordering, and UTF-8 validation. # Motivation The Rust trace model supports span events, but native exporter consumers cannot populate them. This fills the span-event portion of the payload parity work tracked by [APMSP-3219](https://datadoghq.atlassian.net/browse/APMSP-3219). # Additional Notes **Stack position: L3, current PR: [DataDog/libdatadog PR 2301](#2301 These open L0-L5 changes are not included in [libdatadog v38.0.0](https://github.com/DataDog/libdatadog/releases/tag/v38.0.0). They are planned to ship together in a single libdatadog v39 release, with the common dd-trace-rb uptake tracked by [R3 DataDog/dd-trace-rb PR 6143](DataDog/dd-trace-rb#6143). Complete expected libdatadog review and merge order for that single v39 release: | Level | libdatadog PR | Matching dd-trace-rb consumer | | --- | --- | --- | | L0 | [DataDog/libdatadog PR 2302](#2302) | Release prerequisite; no payload API consumer | | L1 | [DataDog/libdatadog PR 2303](#2303) | [R4 DataDog/dd-trace-rb PR 6130](DataDog/dd-trace-rb#6130) | | L2 | [DataDog/libdatadog PR 2305](#2305) | [R5 DataDog/dd-trace-rb PR 6129](DataDog/dd-trace-rb#6129) | | **L3 (current)** | **[DataDog/libdatadog PR 2301](#2301 | **[R6 DataDog/dd-trace-rb PR 6134](DataDog/dd-trace-rb#6134 | | L4 | [DataDog/libdatadog PR 2304](#2304) | [R7 DataDog/dd-trace-rb PR 6132](DataDog/dd-trace-rb#6132) | | L5 | [DataDog/libdatadog PR 2300](#2300) | [R8 DataDog/dd-trace-rb PR 6133](DataDog/dd-trace-rb#6133) | L0-L3 are independent and can be reviewed in parallel. Merging them in the listed order is still recommended because it reduces integration and release-branch conflicts, and lands panic containment before the new payload surfaces. L4 is stacked on L1, and L5 is stacked on L4. The matching payload consumers are [R4 DataDog/dd-trace-rb PR 6130](DataDog/dd-trace-rb#6130), [R5 DataDog/dd-trace-rb PR 6129](DataDog/dd-trace-rb#6129), [R6 DataDog/dd-trace-rb PR 6134](DataDog/dd-trace-rb#6134), [R7 DataDog/dd-trace-rb PR 6132](DataDog/dd-trace-rb#6132), and [R8 DataDog/dd-trace-rb PR 6133](DataDog/dd-trace-rb#6133). All depend through the common v39 uptake in [R3 DataDog/dd-trace-rb PR 6143](DataDog/dd-trace-rb#6143). The downstream review and merge order after R3 is R4, R5, R6, R7, then R8; R7 also depends on R4, and R8 depends on R7. [DataDog/libdatadog-rb v37 PR 65](DataDog/libdatadog-rb#65) and [DataDog/libdatadog-rb v38 PR 66](DataDog/libdatadog-rb#66) are separate ordered prerequisite releases only for [R2 DataDog/dd-trace-rb PR 6131](DataDog/dd-trace-rb#6131) and its `ForkSafeRuntime` uptake. They do not contain the open L0-L5 changes or payload APIs. R3 is stacked on R2, but R3, rather than either prerequisite package, is the common v39 payload-API uptake. L0 tracks [APMSP-3830](https://datadoghq.atlassian.net/browse/APMSP-3830); L1-L5 implement the payload work tracked by [APMSP-3219](https://datadoghq.atlassian.net/browse/APMSP-3219). # How to test the change? Prior local validation completed successfully: - `nix develop --command cargo test -p libdd-data-pipeline-ffi` passed 58 tests, including scalar values, homogeneous typed arrays, empty arrays, ordering, ownership, and atomic failure coverage. - `nix develop --command cargo clippy -p libdd-data-pipeline-ffi --all-targets -- -D warnings` passed. - `nix develop .#nightly --command cargo fmt --all -- --check` passed. - `nix develop --command env LIBDATADOG_VENDOR_OVERRIDE=/tmp/opencode/native-span-events-ruby bundle exec rspec spec/datadog/tracing/transport/native/tracer_span_spec.rb spec/datadog/tracing/transport/native/send_traces_spec.rb spec/datadog/tracing/transport/native/transport_spec.rb spec/datadog/tracing/transport/traces_spec.rb spec/datadog/tracing/span_event_spec.rb spec/datadog/tracing/span_operation_spec.rb` passed 123 native and producer examples, including native wire output and legacy JSON fallback. - Targeted Standard and Steep checks for the native transport and span-event paths passed. [APMSP-3219]: https://datadoghq.atlassian.net/browse/APMSP-3219?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ [APMSP-3830]: https://datadoghq.atlassian.net/browse/APMSP-3830?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ --------- Co-authored-by: Julio <julio.gonzalez@datadoghq.com> Co-authored-by: Edmund Kump <edmund.kump@datadoghq.com> Co-authored-by: Julio Gonzalez <107922352+hoolioh@users.noreply.github.com>

lloeki added the AI Generated PR largely written by AI tools label Jul 30, 2026

lloeki requested review from a team as code owners July 30, 2026 11:02

lloeki mentioned this pull request Jul 30, 2026

Bump libdatadog to 38.0.0 DataDog/dd-trace-rb#6131

Merged

lloeki force-pushed the lloeki/native-panic-containment branch from 7e4e66c to 9a5ee5b Compare July 30, 2026 12:02

ekump requested a review from a team as a code owner August 2, 2026 16:37

lloeki and others added 2 commits August 2, 2026 12:41

also include catch panic feature libdd-library-config-ffi

1137f43

ekump force-pushed the lloeki/native-panic-containment branch from bb2ff51 to 1665e3c Compare August 2, 2026 16:45

github-actions Bot added the ci-build label Aug 2, 2026

add lint check to CI to make sure catch panic feature enabled

1d69a83

ekump force-pushed the lloeki/native-panic-containment branch from 1665e3c to 1d69a83 Compare August 2, 2026 17:00

update example to include non-panic call works correctly too

0a2775a

ekump approved these changes Aug 2, 2026

View reviewed changes

chore: Address PR concerns

7b56f2c

github-actions Bot removed the ci-build label Aug 3, 2026

lloeki mentioned this pull request Aug 3, 2026

Prepare libdatadog 39 payload APIs DataDog/dd-trace-rb#6143

Draft

ekump added 2 commits August 3, 2026 17:34

improve test coverage by validating builder/Cargo.toml contains catch…

3f81ab7

… panic and that all catch panic enabled crates are in the catch panic list

clean up comments

8f71950

ekump reviewed Aug 3, 2026

View reviewed changes

Merge remote-tracking branch 'origin/main' into lloeki/native-panic-c…

365be92

…ontainment

hoolioh approved these changes Aug 4, 2026

View reviewed changes

gh-worker-dd-devflow-36fce6 Bot added mergequeue-status: queued mergequeue-status: in_progress and removed mergequeue-status: queued labels Aug 4, 2026

gh-worker-dd-mergequeue-cf854d Bot merged commit e53d1cf into main Aug 4, 2026
91 checks passed

gh-worker-dd-devflow-36fce6 Bot added mergequeue-status: done and removed mergequeue-status: in_progress labels Aug 4, 2026

gh-worker-dd-mergequeue-cf854d Bot deleted the lloeki/native-panic-containment branch August 4, 2026 08:46

Navigation Menu

Uh oh!

fix(data-pipeline): contain panics in combined FFI - #2302

fix(data-pipeline): contain panics in combined FFI#2302
gh-worker-dd-mergequeue-cf854d[bot] merged 8 commits into
mainfrom
lloeki/native-panic-containment

lloeki commented Jul 30, 2026 •

edited

Loading

Uh oh!

pr-commenter Bot commented Jul 30, 2026 •

edited

Loading

Uh oh!

datadog-datadog-us1-prod Bot commented Jul 30, 2026 •

edited by datadog-prod-us1-6 Bot

Loading

Uh oh!

dd-octo-sts Bot commented Jul 30, 2026 •

edited

Loading

Uh oh!

lloeki commented Jul 30, 2026

Uh oh!

ekump left a comment

Uh oh!

lloeki commented Aug 3, 2026

Uh oh!

ekump Aug 3, 2026

Uh oh!

hoolioh commented Aug 4, 2026

Uh oh!

gh-worker-devflow-routing-ef8351 Bot commented Aug 4, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

lloeki commented Jul 30, 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!

pr-commenter Bot commented Jul 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Benchmarks

Comparison

Candidate

Baseline

Uh oh!

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

Uh oh!

Uh oh!

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

Uh oh!

Artifact Size Benchmark Report

Uh oh!

lloeki commented Jul 30, 2026

Uh oh!

ekump left a comment

Choose a reason for hiding this comment

Uh oh!

lloeki commented Aug 3, 2026

Uh oh!

ekump Aug 3, 2026

Choose a reason for hiding this comment

Uh oh!

hoolioh commented Aug 4, 2026

Uh oh!

gh-worker-devflow-routing-ef8351 Bot commented Aug 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

lloeki commented Jul 30, 2026 •

edited

Loading

pr-commenter Bot commented Jul 30, 2026 •

edited

Loading

datadog-datadog-us1-prod Bot commented Jul 30, 2026 •

edited by datadog-prod-us1-6 Bot

Loading

dd-octo-sts Bot commented Jul 30, 2026 •

edited

Loading

gh-worker-devflow-routing-ef8351 Bot commented Aug 4, 2026 •

edited

Loading