chore(deps): Bump ordered-float from 4.2.2 to 4.3.0

[dependabot[bot]]

Bumps ordered-float from 4.2.2 to 4.3.0.

Release notes

Sourced from ordered-float's releases.

v4.3.0

What's Changed

• feat: optionally integrate with num-cmp by @​tisonkun in reem/rust-ordered-float#155

New Contributors

• @​tisonkun made their first contribution in reem/rust-ordered-float#155

Full Changelog: https://github.com/reem/rust-ordered-float/compare/v4.2.2...v4.3.0

Commits

• c8422ce Version 4.3.0
• 20d8033 Merge pull request #155 from tisonkun/num-cmp
• f89a933 feat: optionally integrate with num-cmp
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions[bot]]

Regression Detector Results

Run ID: 1932488e-2cb8-40c8-98f2-96d3c062b6a5 Metrics dashboard

Baseline: 74134299dd78055921d9705035a6c7b582db462d Comparison: 438bc8b47c294a954fbb8bbb56f573e74ee749d0

Performance changes are noted in the perf column of each table:

• ✅ = significantly better comparison variant performance
• ❌ = significantly worse comparison variant performance
• ➖ = no significant change in performance

Significant changes in experiment optimization goals

Confidence level: 90.00% Effect size tolerance: |Δ mean %| ≥ 5.00%

perf	experiment	goal	Δ mean %	Δ mean % CI	links
✅	otlp_http_to_blackhole	ingress throughput	+5.97	[+5.82, +6.11]
✅	socket_to_socket_blackhole	ingress throughput	+5.04	[+4.98, +5.11]

Experiments ignored for regressions

Regressions in experiments with settings containing `erratic: true` are ignored. | perf | experiment | goal | Δ mean % | Δ mean % CI | links | |------|-------------------|-------------------|----------|-----------------|-------| | ✅ | file_to_blackhole | egress throughput | +15.96 | [+8.37, +23.54] | |

Fine details of change detection per experiment

| perf | experiment | goal | Δ mean % | Δ mean % CI | links | |------|---------------------------------------------------|--------------------|----------|-----------------|-------| | ✅ | file_to_blackhole | egress throughput | +15.96 | [+8.37, +23.54] | | | ✅ | otlp_http_to_blackhole | ingress throughput | +5.97 | [+5.82, +6.11] | | | ✅ | socket_to_socket_blackhole | ingress throughput | +5.04 | [+4.98, +5.11] | | | ➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | +2.54 | [+2.34, +2.75] | | | ➖ | splunk_hec_route_s3 | ingress throughput | +1.87 | [+1.55, +2.18] | | | ➖ | syslog_splunk_hec_logs | ingress throughput | +1.72 | [+1.61, +1.83] | | | ➖ | otlp_grpc_to_blackhole | ingress throughput | +1.65 | [+1.54, +1.77] | | | ➖ | http_to_http_acks | ingress throughput | +1.28 | [+0.06, +2.49] | | | ➖ | fluent_elasticsearch | ingress throughput | +0.99 | [+0.50, +1.49] | | | ➖ | syslog_humio_logs | ingress throughput | +0.48 | [+0.37, +0.58] | | | ➖ | datadog_agent_remap_blackhole | ingress throughput | +0.36 | [+0.25, +0.46] | | | ➖ | http_text_to_http_json | ingress throughput | +0.35 | [+0.19, +0.50] | | | ➖ | http_to_http_noack | ingress throughput | +0.14 | [+0.06, +0.21] | | | ➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | +0.03 | [-0.05, +0.11] | | | ➖ | http_to_http_json | ingress throughput | +0.03 | [-0.01, +0.06] | | | ➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | +0.01 | [-0.08, +0.11] | | | ➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | +0.00 | [-0.10, +0.11] | | | ➖ | http_to_s3 | ingress throughput | -0.01 | [-0.28, +0.27] | | | ➖ | syslog_loki | ingress throughput | -0.01 | [-0.08, +0.07] | | | ➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | -0.62 | [-0.74, -0.50] | | | ➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | -1.20 | [-1.30, -1.10] | | | ➖ | http_elasticsearch | ingress throughput | -1.26 | [-1.40, -1.12] | | | ➖ | syslog_log2metric_humio_metrics | ingress throughput | -1.27 | [-1.40, -1.13] | | | ➖ | datadog_agent_remap_blackhole_acks | ingress throughput | -1.67 | [-1.77, -1.58] | | | ➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | -1.94 | [-2.07, -1.81] | | | ➖ | datadog_agent_remap_datadog_logs | ingress throughput | -2.55 | [-2.75, -2.35] | |

Explanation

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI". For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true: 1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look. 2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that *if our statistical model is accurate*, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants. 3. Its configuration does not mark it "erratic".