fix(remote-config): reuse injected sleep capability

[rochdev]

What does this PR do?

• Reuses the injected SleepCapability for agentless request timeouts.
• Aligns remote-config hashbrown and thiserror versions with the workspace.
• Adds an integration-test assertion that the static sleep constructor is not used.

Motivation

Agentless consumers already provide their HTTP and timer capabilities. Constructing a separate timeout capability forced platform-specific fallback timers in consumers such as libdatadog-nodejs. Aligning shared dependencies also removes avoidable duplicate code from constrained artifacts.

Additional Notes

The libdatadog-nodejs follow-up removes its native/WASM timer split and pins this revision.

How to test the change?

• cargo test -p libdd-remote-config --no-default-features --features agentless,regex-lite
• cargo +stable clippy -p libdd-remote-config --all-targets --no-default-features --features agentless,regex-lite -- -D warnings
• cargo +nightly-2026-07-26 fmt --all -- --check
• ./tools/check_licenses.sh

Generated by Codex.

[datadog-official]

More details

The agentless fetcher now uses the injected capability for HTTP requests and request timeouts. Static inspection finds no concrete failure in the changed source or dependency updates.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 3fa1d13 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[datadog-official]

✅ All CI checks and tests passed.

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 50.00%
• Overall Coverage: 76.67% (-0.02%)

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

[dd-octo-sts]

Artifact Size Benchmark Report

aarch64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a	89.74 MB	89.74 MB	-0% (-808 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so	8.26 MB	8.26 MB	0% (0 B) 👌

aarch64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a	100.97 MB	100.97 MB	+0% (+200 B) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.13 MB	11.13 MB	0% (0 B) 👌

libdatadog-x64-windows

Artifact	Baseline	Commit	Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll	26.68 MB	26.68 MB	0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib	94.96 KB	94.96 KB	0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb	181.16 MB	181.15 MB	-0% (-16.00 KB) 👌
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib	770.91 MB	770.98 MB	+0% (+73.33 KB) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll	8.75 MB	8.75 MB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib	94.96 KB	94.96 KB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb	25.70 MB	25.70 MB	0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib	51.17 MB	51.17 MB	-0% (-224 B) 👌

libdatadog-x86-windows

Artifact	Baseline	Commit	Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll	23.25 MB	23.25 MB	-0% (-512 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib	96.45 KB	96.45 KB	0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb	186.11 MB	186.12 MB	+0% (+16.00 KB) 👌
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib	756.49 MB	756.68 MB	+.02% (+195.80 KB) 🔍
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll	6.76 MB	6.76 MB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib	96.45 KB	96.45 KB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb	27.64 MB	27.64 MB	0% (0 B) 👌
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib	48.71 MB	48.71 MB	-0% (-862 B) 👌

x86_64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a	80.03 MB	80.03 MB	+0% (+256 B) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so	9.18 MB	9.18 MB	0% (0 B) 👌

x86_64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a	95.76 MB	95.76 MB	+0% (+80 B) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.20 MB	11.20 MB	-0% (-8 B) 👌

[pr-commenter]

Benchmarks

Comparison

Benchmark execution time: 2026-08-27 23:19:28

Comparing candidate commit 3fa1d13 in PR branch rochdev/remote-config-dependency-convergence with baseline commit 7327f30 in branch main.

Found 0 performance improvements and 1 performance regressions! Performance is the same for 152 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:vec_map/as_deduped_map/needs_dedup_1_in_2/128

• 🟥 execution_time [+328.132ns; +331.593ns] or [+4.432%; +4.478%]

Benchmark execution time: 2026-08-27 23:26:17

Comparing candidate commit 3fa1d13 in PR branch rochdev/remote-config-dependency-convergence with baseline commit 7327f30 in branch main.

Found 2 performance improvements and 10 performance regressions! Performance is the same for 156 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:alloc_free/system/4096

• 🟥 execution_time [+12.679ns; +12.849ns] or [+15.867%; +16.079%]

scenario:glob_matcher/ascii_case_insensitive_match/wall_time

• 🟥 execution_time [+1.929ns; +1.945ns] or [+7.234%; +7.292%]

scenario:glob_matcher/ascii_exact_match/wall_time

• 🟥 execution_time [+1.924ns; +1.946ns] or [+7.214%; +7.293%]

scenario:glob_matcher/unicode_exact_match/wall_time

• 🟥 execution_time [+4.585ns; +4.660ns] or [+6.217%; +6.318%]

scenario:profiler_attached/fast_path_noop/16

• 🟥 execution_time [+2.825ns; +2.833ns] or [+19.496%; +19.555%]

scenario:profiler_attached/fast_path_noop/256

• 🟥 execution_time [+2.826ns; +2.835ns] or [+19.503%; +19.564%]

scenario:profiler_attached/fast_path_noop/4096

• 🟥 execution_time [+2.827ns; +2.834ns] or [+19.514%; +19.563%]

scenario:profiler_attached/fast_path_noop/64

• 🟥 execution_time [+2.827ns; +2.836ns] or [+19.514%; +19.575%]

scenario:profiler_attached/fast_path_noop/65536

• 🟥 execution_time [+2.827ns; +2.835ns] or [+19.513%; +19.568%]

scenario:profiler_attached/slow_path_system/4096

• 🟥 execution_time [+13.637ns; +13.780ns] or [+8.763%; +8.854%]

scenario:trace_buffer/2_senders/no_delay

• 🟩 execution_time [-231.960µs; -218.666µs] or [-13.461%; -12.689%]
• 🟩 throughput [+152403.998op/s; +161167.642op/s] or [+14.582%; +15.420%]

Candidate

Omitted due to size.

Baseline

Omitted due to size.

[bwoebi]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-28 11:35:32 UTC ℹ️ Start processing command /merge

---

2026-08-28 11:35:37 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-08-28 12:14:51 UTC ℹ️ MergeQueue: This merge request was merged