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

[dependabot[bot]]

trafficstars

Bumps the clap group with 3 updates: clap, clap-verbosity-flag and clap_complete.

Updates clap from 4.4.18 to 4.5.0

Changelog

Sourced from clap's changelog.

[4.5.0] - 2024-02-08

Compatibility

• Update MSRV to 1.74

Commits

• a751c5f chore: Release
• 9ec6c94 chore: Release
• 0735119 docs: Update changelog
• c4d3959 Merge pull request #5344 from epage/encode
• f750e57 fix(lex): Use new-ish OsStr API
• 1d9a554 Merge pull request #5343 from epage/msrv
• 4b45d36 chore: Update MSRV to 1.74
• 55b1f94 Merge pull request #5342 from epage/divan
• ea77b98 test(complete): Make it order independent
• b0fea2b test(bench): Switch to divan
• Additional commits viewable in compare view

Updates clap-verbosity-flag from 2.1.2 to 2.2.0

Changelog

Sourced from clap-verbosity-flag's changelog.

[2.2.0] - 2024-02-14

Compatibility

• Raised MSRV to 1.73

Features

• Add is_present() to see if one of the flags is present on the command-line

Commits

• 42895a2 chore: Release clap-verbosity-flag version 2.2.0
• 527c6e3 docs: Update changelog
• ca600f1 Merge pull request #94 from BTOdell/feature/is_set
• ef15043 Update function name and docs.
• 2fc7470 Add is_set public function.
• 6420685 Merge pull request #92 from clap-rs/renovate/rust-1.x
• 1e32275 chore(deps): update msrv to v1.73
• 84b3db2 Merge pull request #91 from clap-rs/renovate/env_logger-0.x
• bb266d0 chore(deps): update rust crate env_logger to 0.11.1
• 63f6db4 chore(deps): update rust crate clap to 4.4.18
• Additional commits viewable in compare view

Updates clap_complete from 4.4.10 to 4.5.0

Release notes

Sourced from clap_complete's releases.

v4.4.18

[4.4.18] - 2024-01-16

Fixes

• (error) When lacking usage feature, ensure the list of required arguments is unique

v4.4.17

[4.4.17] - 2024-01-15

Fixes

• Fix panic! when mixing args_conflicts_with_subcommands with ArgGroup (which is implicit with derive) introduced in 4.4.15

v4.4.16

[4.4.16] - 2024-01-12

Fixes

• Ensure invalid escape sequences in user-defined strings are correctly stripped when terminal doesn't support color

v4.4.15

[4.4.15] - 2024-01-11

Fixes

• Improve error for args_conflicts_with_subcommands
• Ensure we error for args_conflicts_with_subcommands when using subcommand short and long flags

v4.4.14

[4.4.14] - 2024-01-08

Documentation

• Fix find cookbook entry to allow repeats of flags/options

Features

• Allow num_args(0) on options which allows making them emulate being a flag for position-tracking flags

v4.4.13

[4.4.13] - 2024-01-04

Documentation

• Fix link to structopt migration guide

v4.4.12

[4.4.12] - 2023-12-28

... (truncated)

Changelog

Sourced from clap_complete's changelog.

[4.5.0] - 2024-02-08

Compatibility

• Update MSRV to 1.74

[4.4.18] - 2024-01-16

Fixes

• (error) When lacking usage feature, ensure the list of required arguments is unique

[4.4.17] - 2024-01-15

Fixes

• Fix panic! when mixing args_conflicts_with_subcommands with ArgGroup (which is implicit with derive) introduced in 4.4.15

[4.4.16] - 2024-01-12

Fixes

• Ensure invalid escape sequences in user-defined strings are correctly stripped when terminal doesn't support color

[4.4.15] - 2024-01-11

Fixes

• Improve error for args_conflicts_with_subcommands
• Ensure we error for args_conflicts_with_subcommands when using subcommand short and long flags

[4.4.14] - 2024-01-08

Documentation

• Fix find cookbook entry to allow repeats of flags/options

Features

• Allow num_args(0) on options which allows making them emulate being a flag for position-tracking flags

[4.4.13] - 2024-01-04

Documentation

• Fix link to structopt migration guide

[4.4.12] - 2023-12-28

Performance

... (truncated)

Commits

• a751c5f chore: Release
• 9ec6c94 chore: Release
• 0735119 docs: Update changelog
• c4d3959 Merge pull request #5344 from epage/encode
• f750e57 fix(lex): Use new-ish OsStr API
• 1d9a554 Merge pull request #5343 from epage/msrv
• 4b45d36 chore: Update MSRV to 1.74
• 55b1f94 Merge pull request #5342 from epage/divan
• ea77b98 test(complete): Make it order independent
• b0fea2b test(bench): Switch to divan
• 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[bot]]

Your preview site for the Rust Doc will be ready in a few minutes, please allow time for it to build.

Heres your preview link: Rust Doc preview

[github-actions[bot]]

Your preview site for the VRL Playground will be ready in a few minutes, please allow time for it to build.

Heres your preview link: VRL Playground preview

[github-actions[bot]]

Your preview site for the vector.dev will be ready in a few minutes, please allow time for it to build.

Heres your preview link: vector.dev preview

[datadog-vectordotdev[bot]]

Datadog Report

Branch report: dependabot/cargo/clap-54fd7c26c0 Commit report: 36d4c16 Test service: vector

:white_check_mark: 0 Failed, 2106 Passed, 0 Skipped, 1m 25.57s Wall Time

[github-actions[bot]]

Regression Detector Results

Run ID: 39ad5db1-74c0-43ca-8036-ebae50df3a98 Baseline: 2f1c7850fbc039a894f51b844e919adf2fdc925d Comparison: 9109b461d66efe1f07913f0652776b40416e60da 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

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.

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	syslog_log2metric_humio_metrics	ingress throughput	+3.42	[+3.28, +3.55]
➖	datadog_agent_remap_blackhole	ingress throughput	+2.27	[+2.16, +2.38]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	+1.79	[+1.70, +1.89]
➖	file_to_blackhole	egress throughput	+1.14	[-1.33, +3.61]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	+1.00	[+0.90, +1.10]
➖	splunk_hec_route_s3	ingress throughput	+0.99	[+0.50, +1.48]
➖	otlp_grpc_to_blackhole	ingress throughput	+0.34	[+0.25, +0.42]
➖	http_to_http_noack	ingress throughput	+0.18	[+0.08, +0.27]
➖	http_to_http_json	ingress throughput	+0.03	[-0.05, +0.10]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	+0.00	[-0.14, +0.15]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	-0.00	[-0.16, +0.16]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.05	[-0.17, +0.06]
➖	syslog_humio_logs	ingress throughput	-0.09	[-0.19, +0.01]
➖	enterprise_http_to_http	ingress throughput	-0.12	[-0.20, -0.04]
➖	datadog_agent_remap_datadog_logs	ingress throughput	-0.27	[-0.35, -0.18]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.39	[-0.48, -0.30]
➖	syslog_loki	ingress throughput	-0.48	[-0.52, -0.44]
➖	http_to_s3	ingress throughput	-0.60	[-0.88, -0.32]
➖	http_to_http_acks	ingress throughput	-0.82	[-2.13, +0.48]
➖	syslog_splunk_hec_logs	ingress throughput	-0.90	[-0.98, -0.83]
➖	http_elasticsearch	ingress throughput	-0.94	[-1.01, -0.88]
➖	http_text_to_http_json	ingress throughput	-1.47	[-1.61, -1.33]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-1.70	[-1.87, -1.52]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-1.79	[-1.89, -1.68]
➖	otlp_http_to_blackhole	ingress throughput	-2.51	[-2.65, -2.37]
➖	fluent_elasticsearch	ingress throughput	-2.69	[-3.17, -2.22]
➖	socket_to_socket_blackhole	ingress throughput	-2.90	[-2.97, -2.82]

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: e28d2126-f744-493a-b146-2744810b63db Baseline: 4f0dbf4d2792dc266e0b9ea74158a6a96a1adccb Comparison: 8db5270edad4a54d75a3bf615c861916ff2b4746 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

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.

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	syslog_log2metric_humio_metrics	ingress throughput	+2.77	[+2.64, +2.90]
➖	datadog_agent_remap_blackhole	ingress throughput	+2.43	[+2.33, +2.52]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	+1.86	[+1.76, +1.95]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	+1.82	[+1.68, +1.97]
➖	otlp_http_to_blackhole	ingress throughput	+1.26	[+1.10, +1.41]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	+1.22	[+1.14, +1.31]
➖	http_to_http_acks	ingress throughput	+0.96	[-0.35, +2.27]
➖	splunk_hec_route_s3	ingress throughput	+0.81	[+0.32, +1.30]
➖	otlp_grpc_to_blackhole	ingress throughput	+0.41	[+0.33, +0.50]
➖	datadog_agent_remap_datadog_logs	ingress throughput	+0.38	[+0.30, +0.47]
➖	http_to_http_noack	ingress throughput	+0.15	[+0.06, +0.24]
➖	http_to_http_json	ingress throughput	+0.06	[-0.02, +0.14]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.00	[-0.16, +0.16]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	-0.00	[-0.15, +0.14]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.03	[-0.15, +0.08]
➖	enterprise_http_to_http	ingress throughput	-0.08	[-0.17, +0.00]
➖	http_to_s3	ingress throughput	-0.26	[-0.54, +0.01]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-0.28	[-0.43, -0.12]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-0.31	[-0.42, -0.19]
➖	syslog_splunk_hec_logs	ingress throughput	-0.51	[-0.58, -0.45]
➖	syslog_humio_logs	ingress throughput	-0.65	[-0.75, -0.55]
➖	http_text_to_http_json	ingress throughput	-0.76	[-0.87, -0.65]
➖	fluent_elasticsearch	ingress throughput	-0.92	[-1.39, -0.45]
➖	file_to_blackhole	egress throughput	-1.15	[-3.68, +1.39]
➖	syslog_loki	ingress throughput	-1.48	[-1.55, -1.41]
➖	http_elasticsearch	ingress throughput	-2.35	[-2.42, -2.28]
➖	socket_to_socket_blackhole	ingress throughput	-3.91	[-3.99, -3.84]

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

[bruceg]

@dependabot close

[dependabot[bot]]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.