chore(deps): Bump thiserror from 1.0.63 to 1.0.64

[dependabot[bot]]

Bumps thiserror from 1.0.63 to 1.0.64.

Release notes

Sourced from thiserror's releases.

1.0.64

• Exclude derived impls from coverage instrumentation (#322, thanks @​oxalica)

Commits

• 84484bc Release 1.0.64
• 023f036 Merge pull request #322 from oxalica/feat/mark-auto-derived
• ae1f47e Mark #[automatically_derived] for generated impls
• ab5b5e3 Upload CI Cargo.lock for reproducing failures
• 00b3c14 Work around new dead code warning in test
• 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: fd2bda02-0832-4155-92c4-4c20136de55d Metrics dashboard

Baseline: 62e5ad127bb8cf2aa129902fd185c310f1da937b Comparison: ab8df493c182cd1ca8cfab5b9f7bb99291a5bddd

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
✅	splunk_hec_route_s3	ingress throughput	+5.51	[+5.18, +5.84]

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 | +9.01 | [+1.83, +16.19] | |

Fine details of change detection per experiment

| perf | experiment | goal | Δ mean % | Δ mean % CI | links | |------|---------------------------------------------------|--------------------|----------|-----------------|-------| | ✅ | file_to_blackhole | egress throughput | +9.01 | [+1.83, +16.19] | | | ✅ | splunk_hec_route_s3 | ingress throughput | +5.51 | [+5.18, +5.84] | | | ➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | +3.34 | [+3.22, +3.45] | | | ➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | +2.92 | [+2.72, +3.13] | | | ➖ | datadog_agent_remap_blackhole_acks | ingress throughput | +1.07 | [+0.95, +1.19] | | | ➖ | fluent_elasticsearch | ingress throughput | +0.97 | [+0.47, +1.47] | | | ➖ | http_to_s3 | ingress throughput | +0.38 | [+0.09, +0.66] | | | ➖ | http_to_http_acks | ingress throughput | +0.37 | [-0.86, +1.60] | | | ➖ | syslog_log2metric_humio_metrics | ingress throughput | +0.36 | [+0.23, +0.49] | | | ➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | +0.18 | [+0.02, +0.33] | | | ➖ | http_to_http_noack | ingress throughput | +0.18 | [+0.09, +0.26] | | | ➖ | datadog_agent_remap_blackhole | ingress throughput | +0.13 | [+0.01, +0.25] | | | ➖ | http_to_http_json | ingress throughput | +0.09 | [+0.02, +0.15] | | | ➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | +0.01 | [-0.08, +0.10] | | | ➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | +0.01 | [-0.08, +0.10] | | | ➖ | http_text_to_http_json | ingress throughput | -0.16 | [-0.28, -0.03] | | | ➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.36 | [-0.47, -0.25] | | | ➖ | syslog_splunk_hec_logs | ingress throughput | -0.57 | [-0.68, -0.47] | | | ➖ | syslog_humio_logs | ingress throughput | -0.90 | [-1.04, -0.76] | | | ➖ | syslog_loki | ingress throughput | -0.93 | [-1.07, -0.80] | | | ➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | -1.09 | [-1.21, -0.97] | | | ➖ | datadog_agent_remap_datadog_logs | ingress throughput | -1.15 | [-1.33, -0.98] | | | ➖ | otlp_grpc_to_blackhole | ingress throughput | -1.35 | [-1.48, -1.22] | | | ➖ | http_elasticsearch | ingress throughput | -3.56 | [-3.76, -3.37] | | | ➖ | otlp_http_to_blackhole | ingress throughput | -4.03 | [-4.17, -3.88] | | | ➖ | socket_to_socket_blackhole | ingress throughput | -4.88 | [-4.96, -4.81] | |

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".

[github-actions[bot]]

Regression Detector Results

Run ID: 1b7d9c09-6734-45df-922e-e30a5a183eed Metrics dashboard

Baseline: e17273230a206d5afd23decfba329beb74bfb1c9 Comparison: b0d122ba0658c8e5d7a6542a388906839e0e295a

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

No significant changes in experiment optimization goals

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

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

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 | -21.34 | [-27.29, -15.39] | |

Fine details of change detection per experiment

| perf | experiment | goal | Δ mean % | Δ mean % CI | links | |------|---------------------------------------------------|--------------------|----------|------------------|-------| | ➖ | syslog_log2metric_humio_metrics | ingress throughput | +3.34 | [+3.17, +3.52] | | | ➖ | splunk_hec_route_s3 | ingress throughput | +2.28 | [+1.91, +2.65] | | | ➖ | fluent_elasticsearch | ingress throughput | +2.01 | [+1.52, +2.50] | | | ➖ | syslog_humio_logs | ingress throughput | +1.03 | [+0.89, +1.17] | | | ➖ | otlp_http_to_blackhole | ingress throughput | +0.84 | [+0.69, +0.99] | | | ➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | +0.45 | [+0.29, +0.61] | | | ➖ | socket_to_socket_blackhole | ingress throughput | +0.32 | [+0.23, +0.41] | | | ➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | +0.02 | [-0.07, +0.12] | | | ➖ | http_to_http_noack | ingress throughput | +0.02 | [-0.02, +0.05] | | | ➖ | http_to_http_json | ingress throughput | +0.01 | [-0.05, +0.07] | | | ➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.00 | [-0.09, +0.09] | | | ➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | -0.01 | [-0.10, +0.09] | | | ➖ | http_to_http_acks | ingress throughput | -0.50 | [-1.72, +0.72] | | | ➖ | syslog_splunk_hec_logs | ingress throughput | -0.53 | [-0.62, -0.45] | | | ➖ | datadog_agent_remap_blackhole | ingress throughput | -0.65 | [-0.77, -0.53] | | | ➖ | otlp_grpc_to_blackhole | ingress throughput | -0.81 | [-0.95, -0.67] | | | ➖ | datadog_agent_remap_datadog_logs | ingress throughput | -0.94 | [-1.10, -0.78] | | | ➖ | http_elasticsearch | ingress throughput | -0.94 | [-1.14, -0.75] | | | ➖ | http_text_to_http_json | ingress throughput | -1.38 | [-1.62, -1.15] | | | ➖ | http_to_s3 | ingress throughput | -1.41 | [-1.68, -1.14] | | | ➖ | syslog_loki | ingress throughput | -1.63 | [-1.72, -1.55] | | | ➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | -1.87 | [-1.99, -1.74] | | | ➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | -2.58 | [-2.72, -2.44] | | | ➖ | datadog_agent_remap_blackhole_acks | ingress throughput | -2.70 | [-2.90, -2.51] | | | ➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | -2.82 | [-2.99, -2.66] | | | ❌ | file_to_blackhole | egress throughput | -21.34 | [-27.29, -15.39] | |

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".

[github-actions[bot]]

Regression Detector Results

Run ID: b7b9de57-ab81-4cef-813a-206c857922af Metrics dashboard

Baseline: 0b047518d5ad550ff4bef61a06edc70c0348868d Comparison: d87c8fa02027589b19ed36b5dc63c177defc1e46

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

No significant changes in experiment optimization goals

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

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

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.30 | [+7.50, +23.09] | |

Fine details of change detection per experiment

| perf | experiment | goal | Δ mean % | Δ mean % CI | links | |------|---------------------------------------------------|--------------------|----------|-----------------|-------| | ✅ | file_to_blackhole | egress throughput | +15.30 | [+7.50, +23.09] | | | ➖ | socket_to_socket_blackhole | ingress throughput | +3.17 | [+3.12, +3.22] | | | ➖ | otlp_http_to_blackhole | ingress throughput | +2.27 | [+2.15, +2.39] | | | ➖ | http_text_to_http_json | ingress throughput | +1.44 | [+1.33, +1.55] | | | ➖ | http_to_http_acks | ingress throughput | +1.27 | [+0.04, +2.51] | | | ➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | +0.36 | [+0.25, +0.46] | | | ➖ | http_to_s3 | ingress throughput | +0.32 | [+0.04, +0.59] | | | ➖ | otlp_grpc_to_blackhole | ingress throughput | +0.15 | [+0.04, +0.26] | | | ➖ | http_to_http_noack | ingress throughput | +0.10 | [+0.03, +0.17] | | | ➖ | http_to_http_json | ingress throughput | +0.02 | [-0.01, +0.06] | | | ➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | +0.01 | [-0.07, +0.09] | | | ➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | +0.01 | [-0.08, +0.10] | | | ➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.00 | [-0.10, +0.10] | | | ➖ | syslog_humio_logs | ingress throughput | -0.03 | [-0.12, +0.07] | | | ➖ | fluent_elasticsearch | ingress throughput | -0.10 | [-0.59, +0.40] | | | ➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | -0.57 | [-0.69, -0.45] | | | ➖ | datadog_agent_remap_blackhole_acks | ingress throughput | -0.59 | [-0.69, -0.50] | | | ➖ | datadog_agent_remap_datadog_logs | ingress throughput | -0.60 | [-0.82, -0.38] | | | ➖ | syslog_splunk_hec_logs | ingress throughput | -0.77 | [-0.87, -0.66] | | | ➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | -1.10 | [-1.21, -0.99] | | | ➖ | datadog_agent_remap_blackhole | ingress throughput | -1.17 | [-1.29, -1.05] | | | ➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | -1.24 | [-1.41, -1.07] | | | ➖ | syslog_loki | ingress throughput | -1.42 | [-1.50, -1.34] | | | ➖ | splunk_hec_route_s3 | ingress throughput | -2.01 | [-2.32, -1.70] | | | ➖ | syslog_log2metric_humio_metrics | ingress throughput | -2.24 | [-2.38, -2.11] | | | ➖ | http_elasticsearch | ingress throughput | -3.16 | [-3.32, -3.00] | |

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".

[github-actions[bot]]

Regression Detector Results

Run ID: 77a0bbc9-3fce-447b-8e16-4b4960852062 Metrics dashboard

Baseline: 3d2f5c871f3dcd4affc9e13a9ce34a1b3df37bfb Comparison: 800fd9a97eb12d49161dfdd117521f2bf65ec4f0

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

No significant changes in experiment optimization goals

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

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

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 | +10.02 | [+2.67, +17.38] | |

Fine details of change detection per experiment

| perf | experiment | goal | Δ mean % | Δ mean % CI | links | |------|---------------------------------------------------|--------------------|----------|-----------------|-------| | ✅ | file_to_blackhole | egress throughput | +10.02 | [+2.67, +17.38] | | | ➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | +3.99 | [+3.87, +4.12] | | | ➖ | syslog_log2metric_humio_metrics | ingress throughput | +3.19 | [+3.04, +3.34] | | | ➖ | otlp_http_to_blackhole | ingress throughput | +2.48 | [+2.35, +2.61] | | | ➖ | datadog_agent_remap_datadog_logs | ingress throughput | +1.54 | [+1.36, +1.72] | | | ➖ | syslog_loki | ingress throughput | +1.48 | [+1.42, +1.55] | | | ➖ | syslog_humio_logs | ingress throughput | +0.96 | [+0.86, +1.06] | | | ➖ | http_elasticsearch | ingress throughput | +0.87 | [+0.71, +1.04] | | | ➖ | socket_to_socket_blackhole | ingress throughput | +0.73 | [+0.68, +0.78] | | | ➖ | otlp_grpc_to_blackhole | ingress throughput | +0.67 | [+0.56, +0.79] | | | ➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | +0.50 | [+0.43, +0.58] | | | ➖ | fluent_elasticsearch | ingress throughput | +0.28 | [-0.22, +0.78] | | | ➖ | splunk_hec_route_s3 | ingress throughput | +0.15 | [-0.15, +0.46] | | | ➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | +0.09 | [-0.05, +0.22] | | | ➖ | http_to_http_json | ingress throughput | +0.02 | [-0.01, +0.05] | | | ➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | +0.01 | [-0.08, +0.10] | | | ➖ | http_to_http_noack | ingress throughput | +0.00 | [-0.02, +0.02] | | | ➖ | datadog_agent_remap_blackhole_acks | ingress throughput | -0.00 | [-0.11, +0.11] | | | ➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.01 | [-0.10, +0.08] | | | ➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | -0.03 | [-0.12, +0.05] | | | ➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | -0.12 | [-0.24, -0.00] | | | ➖ | http_to_s3 | ingress throughput | -0.26 | [-0.53, +0.01] | | | ➖ | syslog_splunk_hec_logs | ingress throughput | -0.56 | [-0.63, -0.48] | | | ➖ | http_to_http_acks | ingress throughput | -0.61 | [-1.83, +0.62] | | | ➖ | http_text_to_http_json | ingress throughput | -1.03 | [-1.15, -0.90] | | | ➖ | datadog_agent_remap_blackhole | ingress throughput | -1.70 | [-1.81, -1.59] | |

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".