chore(deps): Bump the clap group with 2 updates

[dependabot]

Bumps the clap group with 2 updates: clap and clap_complete.

Updates clap from 4.4.11 to 4.4.12

Release notes

Sourced from clap's releases.

v4.4.12

[4.4.12] - 2023-12-28

Performance

• Only ask TypedValueParser for possible values if needed

Changelog

Sourced from clap's changelog.

[4.4.12] - 2023-12-28

Performance

• Only ask TypedValueParser for possible values if needed

Commits

• 6d601e6 chore: Release
• 048e7f0 docs: Update changelog
• 53f5b82 Merge pull request #5267 from vermiculus/sa/avoid-pv-expansion-in-help
• 05cd057 perf: Avoid retrieving possible_values unless used
• 2920808 test: Update snapshots
• 28763eb chore: Release
• ace7bb5 docs(complete): Update changelog
• 76beca4 docs(complete): Polish API reference for dynamic
• 3630e58 Merge pull request #5273 from epage/docsrs
• 3724b9e docs: Include more content on docs.rs
• See full diff in compare view

Updates clap_complete from 4.4.4 to 4.4.6

Release notes

Sourced from clap_complete's releases.

v4.4.6

[4.4.6] - 2023-09-28

Internal

• Upgrade anstream

v4.4.5

[4.4.5] - 2023-09-25

Fixes

• (parser) When inferring subcommand name or long_flag, allow ambiguous-looking matches that unambiguously map back to the same command
• (parser) When inferring subcommand long_flag, don't panic
• (assert) Clarify what action is causing a positional that doesn't set values which is especially useful for derive users

Changelog

Sourced from clap_complete's changelog.

[4.4.6] - 2023-09-28

Internal

• Upgrade anstream

[4.4.5] - 2023-09-25

Fixes

• (parser) When inferring subcommand name or long_flag, allow ambiguous-looking matches that unambiguously map back to the same command
• (parser) When inferring subcommand long_flag, don't panic
• (assert) Clarify what action is causing a positional that doesn't set values which is especially useful for derive users

Commits

• 48d28aa chore: Release
• 748ce18 docs: Update changelog
• adbe6ec Merge pull request #5278 from henry-hsieh/fix-nosort
• 2b48858 fix: Skip nosort option below bash 4.4
• 777b744 Merge pull request #5277 from clap-rs/renovate/actions-setup-python-5.x
• 924b252 chore(deps): update compatible (dev) (#5276)
• b8cc508 chore(deps): update actions/setup-python action to v5
• 6d601e6 chore: Release
• 048e7f0 docs: Update changelog
• 53f5b82 Merge pull request #5267 from vermiculus/sa/avoid-pv-expansion-in-help
• Additional commits viewable 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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[github-actions]

Regression Detector Results

Run ID: e22abca7-b0aa-488d-a022-b0e06483a50c
Baseline: e255e6d
Comparison: d73fd6f
Total CPUs: 7

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
✅	syslog_regex_logs2metric_ddmetrics	ingress throughput	+10.89	[+10.19, +11.58]
❌	otlp_http_to_blackhole	ingress throughput	-5.10	[-5.25, -4.96]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
✅	syslog_regex_logs2metric_ddmetrics	ingress throughput	+10.89	[+10.19, +11.58]
➖	syslog_log2metric_humio_metrics	ingress throughput	+4.86	[+4.70, +5.02]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	+0.96	[+0.88, +1.05]
➖	splunk_hec_route_s3	ingress throughput	+0.75	[+0.24, +1.26]
➖	http_to_s3	ingress throughput	+0.27	[-0.01, +0.54]
➖	datadog_agent_remap_blackhole	ingress throughput	+0.26	[+0.17, +0.35]
➖	datadog_agent_remap_datadog_logs	ingress throughput	+0.26	[+0.17, +0.35]
➖	http_to_http_noack	ingress throughput	+0.14	[+0.05, +0.23]
➖	syslog_humio_logs	ingress throughput	+0.08	[-0.02, +0.18]
➖	http_to_http_json	ingress throughput	+0.04	[-0.03, +0.12]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.00	[-0.14, +0.15]
➖	http_to_http_acks	ingress throughput	-0.00	[-1.31, +1.31]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	-0.00	[-0.14, +0.14]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.03	[-0.14, +0.08]
➖	enterprise_http_to_http	ingress throughput	-0.14	[-0.24, -0.05]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	-0.23	[-0.33, -0.14]
➖	file_to_blackhole	egress throughput	-0.24	[-2.63, +2.15]
➖	otlp_grpc_to_blackhole	ingress throughput	-0.44	[-0.53, -0.34]
➖	http_elasticsearch	ingress throughput	-0.52	[-0.58, -0.45]
➖	http_text_to_http_json	ingress throughput	-0.69	[-0.83, -0.55]
➖	syslog_loki	ingress throughput	-1.61	[-1.69, -1.53]
➖	fluent_elasticsearch	ingress throughput	-1.75	[-2.23, -1.28]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-1.92	[-2.04, -1.80]
➖	syslog_splunk_hec_logs	ingress throughput	-2.26	[-2.33, -2.18]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-2.59	[-2.73, -2.45]
➖	socket_to_socket_blackhole	ingress throughput	-2.60	[-2.67, -2.53]
❌	otlp_http_to_blackhole	ingress throughput	-5.10	[-5.25, -4.96]

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]

Regression Detector Results

Run ID: 69d7390f-cf82-4542-afa4-0468bf8df465
Baseline: dad8a85
Comparison: 0f29afa
Total CPUs: 7

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
✅	datadog_agent_remap_blackhole_acks	ingress throughput	+9.23	[+8.54, +9.92]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
✅	datadog_agent_remap_blackhole_acks	ingress throughput	+9.23	[+8.54, +9.92]
➖	syslog_splunk_hec_logs	ingress throughput	+1.42	[+1.35, +1.50]
➖	splunk_hec_route_s3	ingress throughput	+1.09	[+0.57, +1.61]
➖	http_to_http_acks	ingress throughput	+0.95	[-0.37, +2.28]
➖	syslog_log2metric_humio_metrics	ingress throughput	+0.84	[+0.72, +0.96]
➖	http_to_s3	ingress throughput	+0.51	[+0.23, +0.78]
➖	otlp_grpc_to_blackhole	ingress throughput	+0.27	[+0.17, +0.37]
➖	http_elasticsearch	ingress throughput	+0.21	[+0.14, +0.27]
➖	http_to_http_noack	ingress throughput	+0.15	[+0.06, +0.24]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	+0.04	[-0.06, +0.14]
➖	http_to_http_json	ingress throughput	+0.03	[-0.04, +0.11]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	-0.00	[-0.15, +0.14]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	-0.00	[-0.14, +0.14]
➖	datadog_agent_remap_datadog_logs	ingress throughput	-0.03	[-0.13, +0.06]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.04	[-0.15, +0.08]
➖	syslog_loki	ingress throughput	-0.11	[-0.19, -0.03]
➖	enterprise_http_to_http	ingress throughput	-0.14	[-0.21, -0.07]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.21	[-0.28, -0.13]
➖	fluent_elasticsearch	ingress throughput	-0.84	[-1.31, -0.37]
➖	otlp_http_to_blackhole	ingress throughput	-1.02	[-1.18, -0.86]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-1.10	[-1.24, -0.95]
➖	datadog_agent_remap_blackhole	ingress throughput	-1.22	[-1.31, -1.13]
➖	socket_to_socket_blackhole	ingress throughput	-1.29	[-1.37, -1.22]
➖	http_text_to_http_json	ingress throughput	-1.71	[-1.83, -1.59]
➖	syslog_humio_logs	ingress throughput	-2.04	[-2.15, -1.94]
➖	file_to_blackhole	egress throughput	-2.28	[-4.71, +0.14]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-3.23	[-3.36, -3.10]

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