chore(deps): update cargo pre-1.0 breaking updates to 0.7

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
tikv-jemallocator	workspace.dependencies	minor	0.6 → 0.7
tokio-vsock	workspace.dependencies	minor	0.6 → 0.7

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Cargo breaking update (pre-v1.0) — 0.x → 0.y is a breaking change in Cargo's semver. Before merging, verify the workspace compiles and check upstream release notes for removed features or API changes.

---

Release Notes

tikv/jemallocator (tikv-jemallocator)

v0.7.0

Compare Source

• Reverse order of MAKEFLAGS priority (#​152)
• Define ALIGNOF_MAX_ALIGN_T for riscv32 (#​153)
• Remove build directory once build of jemalloc-sys finishes (#​119)
• Fix cross-compile for tier-3 riscv64a23 target (#​141)
• sys: support *-windows-gnullvm targets (#​150)
• Propagate LDFLAGS, if present (#​155)
• jemalloc-ctl: fix invalid update implementation
• add new free ffi
• Update jemalloc to 5.3.1 (#​161)
• Add profiling_libunwind feature (#​159)
• passthrough cc env/args using native cc features (#​158)

rust-vsock/tokio-vsock (tokio-vsock)

v0.7.2

Compare Source

v0.7.1

Compare Source

v0.7.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[pr-commenter]

Binary Size Analysis (Agent Data Plane)

Baseline: 06d0a65 · Comparison: 402ee3e · diff
Analysis Configuration: stripped binaries · Pass/Fail Threshold: +5%
Sizes: 38.01 MiB (baseline) vs 38.10 MiB (comparison)
Size Change: +89.16 KiB (+0.23%)

✅ Binary size difference within threshold

Changes by Module

Module	File Size	Symbols
figment	+11.56 KiB	687
_rjem_je_arena_ptr_array_flush	+7.96 KiB	1
saluki_io::deser::framing	+4.47 KiB	43
malloc_conf_init_helper	+4.40 KiB	1
ctl_arena_stats_sdmerge	-4.40 KiB	1
ctl_arena_refresh	+4.39 KiB	1
anon.ae75cd3060d8b952a6fd466cba97c1c5.103.llvm.298110800033293764	-3.99 KiB	1
anon.1fe986bc6a40959ac830271fa41edca5.77.llvm.17161955399695731022	+3.99 KiB	1
saluki_components::sources::dogstatsd	-3.98 KiB	337
[sections]	+3.98 KiB	10
_rjem_je_tcache_bin_flush_stashed	-3.86 KiB	1
anon.833b6a0935915f892603f5d7a9fc6534.220.llvm.18260048508852717064	-3.06 KiB	1
anon.8e59832ca43d313a8329d0f6d1d6378a.2.llvm.16012366112733670776	+3.06 KiB	1
stats_general_print	+3.01 KiB	1
stats_arena_extents_print	+2.90 KiB	1
saluki_io::net::client	-2.66 KiB	70
saluki_io::net::util	+2.63 KiB	180
tcache_try_gc_bin	+2.62 KiB	1
mallocx	+2.58 KiB	1
anon.96b0bcf654077b845299e3b26de651aa.141.llvm.9787509115580265217	+2.55 KiB	1

Detailed Symbol Changes

    FILE SIZE        VM SIZE    
 --------------  -------------- 
  [NEW]  +148Ki  [NEW]  +148Ki    agent_data_plane::cli::run::handle_run_command::_{{closure}}::h6a64e8448c7afcaa
  +0.5% +89.5Ki  +0.6% +83.3Ki    [40166 Others]
  [NEW] +84.5Ki  [NEW] +84.3Ki    agent_data_plane::cli::dogstatsd::handle_dogstatsd_command::_{{closure}}::he1a0b0d8b43e3211
  [NEW] +67.1Ki  [NEW] +66.9Ki    agent_data_plane::cli::run::create_topology::_{{closure}}::hca5ea8f6d7d896ed
  [NEW] +65.3Ki  [NEW] +65.1Ki    saluki_core::topology::built::BuiltTopology::spawn::_{{closure}}::hb76af51dc2b630c5
  [NEW] +57.9Ki  [NEW] +57.8Ki    saluki_core::topology::blueprint::TopologyBlueprint::build::_{{closure}}::h96f3a54c51171b29
  [NEW] +56.9Ki  [NEW] +56.7Ki    agent_data_plane::cli::debug::handle_debug_command::_{{closure}}::h2d4d296a58deb842
  [NEW] +55.7Ki  [NEW] +55.6Ki    core::ops::function::FnOnce::call_once::ha595fa249ea49259
  [NEW] +49.3Ki  [NEW] +48.9Ki    agent_data_plane::main::_{{closure}}::h3032207dd914e498
  [NEW] +47.7Ki  [NEW] +47.6Ki    saluki_components::common::datadog::io::run_endpoint_io_loop::_{{closure}}::hc31e413525af5fa5
  [NEW] +38.4Ki  [NEW] +38.2Ki    agent_data_plane::internal::env::workload::build_collector::_{{closure}}::h8a521b4f9936418a
  [DEL] -38.4Ki  [DEL] -38.2Ki    agent_data_plane::internal::env::workload::build_collector::_{{closure}}::h8518305f145d7e76
  [DEL] -48.1Ki  [DEL] -47.9Ki    saluki_components::common::datadog::io::run_endpoint_io_loop::_{{closure}}::h6760b52a19241012
  [DEL] -49.3Ki  [DEL] -48.9Ki    agent_data_plane::main::_{{closure}}::hf71541579e01974b
  [DEL] -55.7Ki  [DEL] -55.6Ki    core::ops::function::FnOnce::call_once::h5866b2464ddf0637
  [DEL] -56.9Ki  [DEL] -56.7Ki    agent_data_plane::cli::debug::handle_debug_command::_{{closure}}::hbd804be8c7f9a296
  [DEL] -57.9Ki  [DEL] -57.8Ki    saluki_core::topology::blueprint::TopologyBlueprint::build::_{{closure}}::hbf871b3913e42c66
  [DEL] -65.3Ki  [DEL] -65.1Ki    saluki_core::topology::built::BuiltTopology::spawn::_{{closure}}::he1098066cae96b1f
  [DEL] -67.1Ki  [DEL] -66.9Ki    agent_data_plane::cli::run::create_topology::_{{closure}}::h9f7e26f20fddfdc1
  [DEL] -84.5Ki  [DEL] -84.3Ki    agent_data_plane::cli::dogstatsd::handle_dogstatsd_command::_{{closure}}::h995e90a0721b5a8b
  [DEL]  -148Ki  [DEL]  -148Ki    agent_data_plane::cli::run::handle_run_command::_{{closure}}::h0215ea3520b410a0
  +0.2% +89.2Ki  +0.3% +82.9Ki    TOTAL

[datadog-datadog-prod-us1]

✨ Fix all issues with BitsAI

⚠️ Warnings

🚦 1 Pipeline job failed

DataDog/saluki | run-benchmarks-adp     

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 402ee3e | Docs | Datadog PR Page | Give us feedback!}

[pr-commenter]

Regression Detector (Agent Data Plane)

Run ID: c84efdea-ef99-464c-96ea-328a3bbfb534
Baseline: 06d0a651 · Comparison: 402ee3e2 · diff

Optimization Goals: ❌ 3 regressions detected

experiment	goal	Δ mean %	links
otlp_ingest_metrics_5mb_memory	memory	🔴 +7.42	metrics profiles logs
dsd_uds_500mb_3k_contexts_memory	memory	🔴 +6.19	metrics profiles logs
dsd_uds_10mb_3k_contexts_memory	memory	🔴 +5.36	metrics profiles logs

Fine details of change detection per experiment (32)

Experiments configured erratic: true are tagged (ignored) and skipped when determining which experiments regressed or improved. Experiments which are detected as erratic at runtime are tagged (erratic) to flag that the run's sample dispersion was high, but their regression / improvement signal still counts.

experiment	goal	Δ mean %	links
otlp_ingest_logs_5mb_memory (ignored)	memory	⚪ +25.96	metrics profiles logs
dsd_uds_100mb_3k_contexts_memory	memory	⚪ +4.85	metrics profiles logs
quality_gates_rss_dsd_medium	memory	⚪ +4.80	metrics profiles logs
quality_gates_rss_dsd_ultraheavy	memory	⚪ +2.81	metrics profiles logs
dsd_uds_1mb_3k_contexts_memory	memory	⚪ +2.80	metrics profiles logs
quality_gates_rss_dsd_heavy	memory	⚪ +2.59	metrics profiles logs
dsd_uds_512kb_3k_contexts_memory	memory	⚪ +2.52	metrics profiles logs
otlp_ingest_traces_ottl_transform_5mb_memory	memory	⚪ +2.29	metrics profiles logs
quality_gates_rss_dsd_low	memory	⚪ +2.26	metrics profiles logs
otlp_ingest_traces_5mb_memory	memory	⚪ +2.16	metrics profiles logs
otlp_ingest_traces_ottl_filtering_5mb_memory	memory	⚪ +2.12	metrics profiles logs
quality_gates_rss_idle	memory	⚪ +1.27	metrics profiles logs
dsd_uds_1mb_3k_contexts_cpu (erratic)	cpu	⚪ +0.28	metrics profiles logs
dsd_uds_512kb_3k_contexts_throughput	throughput	⚪ -0.00	metrics profiles logs
dsd_uds_1mb_3k_contexts_throughput	throughput	⚪ +0.00	metrics profiles logs
dsd_uds_100mb_3k_contexts_throughput	throughput	⚪ +0.01	metrics profiles logs
otlp_ingest_logs_5mb_throughput (ignored)	throughput	⚪ +0.02	metrics profiles logs
dsd_uds_10mb_3k_contexts_throughput	throughput	⚪ +0.02	metrics profiles logs
otlp_ingest_metrics_5mb_throughput	throughput	⚪ +0.03	metrics profiles logs
dsd_uds_500mb_3k_contexts_cpu (erratic)	cpu	⚪ -0.04	metrics profiles logs
otlp_ingest_traces_ottl_transform_5mb_cpu (erratic)	cpu	⚪ -0.11	metrics profiles logs
otlp_ingest_traces_ottl_filtering_5mb_throughput	throughput	⚪ +0.18	metrics profiles logs
otlp_ingest_traces_ottl_transform_5mb_throughput	throughput	⚪ +0.20	metrics profiles logs
otlp_ingest_traces_5mb_cpu (erratic)	cpu	⚪ -0.35	metrics profiles logs
otlp_ingest_traces_ottl_filtering_5mb_cpu (erratic)	cpu	⚪ -0.53	metrics profiles logs
otlp_ingest_traces_5mb_throughput	throughput	⚪ +0.53	metrics profiles logs
otlp_ingest_logs_5mb_cpu (ignored)	cpu	⚪ -2.41	metrics profiles logs
dsd_uds_512kb_3k_contexts_cpu (erratic)	cpu	⚪ -4.81	metrics profiles logs
dsd_uds_100mb_3k_contexts_cpu (erratic)	cpu	🟢 -6.33	metrics profiles logs
dsd_uds_10mb_3k_contexts_cpu (erratic)	cpu	🟢 -7.44	metrics profiles logs
otlp_ingest_metrics_5mb_cpu (erratic)	cpu	🟢 -7.66	metrics profiles logs
dsd_uds_500mb_3k_contexts_throughput	throughput	🟢 +10.00	metrics profiles logs

Bounds Checks: ✅ Passed (5)

experiment	check	replicates	observed	links
quality_gates_rss_dsd_heavy	memory_usage	10/10	✅ 136 MiB ≤ 140 MiB	metrics profiles logs
quality_gates_rss_dsd_low	memory_usage	10/10	✅ 41 MiB ≤ 50 MiB	metrics profiles logs
quality_gates_rss_dsd_medium	memory_usage	10/10	✅ 64.5 MiB ≤ 75 MiB	metrics profiles logs
quality_gates_rss_dsd_ultraheavy	memory_usage	10/10	✅ 191 MiB ≤ 200 MiB	metrics profiles logs
quality_gates_rss_idle	memory_usage	10/10	✅ 27 MiB ≤ 40 MiB	metrics profiles logs

Explanation

A change is flagged as a regression when |Δ mean %| > 5.00% in the regressing direction for its optimization goal AND SMP marks the experiment as a regression (is_regression: true). Improvements use the matching criteria for the improving direction. Experiments configured erratic: true (tagged (ignored)) are skipped outright; experiments detected as erratic at runtime (tagged (erratic)) still count, since that flag describes sample dispersion rather than directional certainty. The Δ mean % cell is colored accordingly: 🟢 = improvement, 🔴 = regression, ⚪ = neutral. Reduction in CPU or memory is an improvement; reduction in ingress throughput is a regression.