You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adds libdd-http-lite, a lightweight, transport-agnostic, no_std-first HTTP layer built on reqwless.
The default configuration does not enable allocation, DNS, sockets, threads, locks, TLS, or a runtime. The crate provides:
low-level reqwless request and response types;
Datadog telemetry metrics helpers as its first protocol-specific request family; and
an optional libc DNS helper for setup code.
Motivation
Some libdatadog consumers need to own the complete I/O stack: transport, buffers, connection setup, and the point at which platform operations occur. A high-level HTTP client necessarily owns more of those decisions.
This crate introduces a small layer for HTTP message construction while leaving networking and execution policy to the caller.
Additional Notes
This crate does not claim that every use is signal-safe. It controls its own default dependency and feature footprint; callers remain responsible for the safety of their transport, buffers, and platform operations in their execution context.
Feature
Default
Purpose
alloc
No
Enables allocation-backed setup helpers.
std
No
Reserves standard-library support and implies alloc.
libc-dns
No
Adds weakly loaded getaddrinfo support for setup paths; it is not signal-safe.
This report tracks Clippy allow annotations for specific rules, showing how they've changed in this PR. Decreasing the number of these annotations generally improves code quality.
Comparing candidate commit 4052698 in PR branch signal_safe_telemetry_metrics_submission with baseline commit e026a3c in branch main.
Found 2 performance improvements and 4 performance regressions! Performance is the same for 136 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:msgpack_decoder::v05/low_sharing/200
🟥 execution_time [+16.942µs; +17.185µs] or [+4.899%; +4.969%]
🟥 throughput [-27390.900op/s; -27000.320op/s] or [-4.736%; -4.669%]
pawelchcki
changed the title
feat(http): add no_std request primitives
feat(http-lite): add no_std HTTP helpers
Jul 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Adds
libdd-http-lite, a lightweight, transport-agnostic,no_std-first HTTP layer built onreqwless.The default configuration does not enable allocation, DNS, sockets, threads, locks, TLS, or a runtime. The crate provides:
reqwlessrequest and response types;Motivation
Some libdatadog consumers need to own the complete I/O stack: transport, buffers, connection setup, and the point at which platform operations occur. A high-level HTTP client necessarily owns more of those decisions.
This crate introduces a small layer for HTTP message construction while leaving networking and execution policy to the caller.
Additional Notes
This crate does not claim that every use is signal-safe. It controls its own default dependency and feature footprint; callers remain responsible for the safety of their transport, buffers, and platform operations in their execution context.
allocstdalloc.libc-dnsgetaddrinfosupport for setup paths; it is not signal-safe.How to test the change?