chore(deps): Bump serde_with from 3.5.0 to 3.5.1

[dependabot]

Bumps serde_with from 3.5.0 to 3.5.1.

Release notes

Sourced from serde_with's releases.

serde_with v3.5.1

Fixed

• The serde_as macro now better detects existing schemars attributes on fields and incorporates them by @​swlynch99 (#682) This avoids errors on existing #[schemars(with = ...)] annotations.

Commits

• 88e9879 Merge pull request #682 from swlynch99/schemars-custom-with
• 1c9131f Bump version to 3.5.1
• bceb16e Add changelog
• 215d77a Use #[serde_as] from import without crate name
• b2afd76 Extend the test with an always existing condition
• c09f33b Avoid emitting a #[schemars] annotation when one already exists
• 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 <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

[datadog-vectordotdev]

Datadog Report

Branch report: dependabot/cargo/serde_with-3.5.1
Commit report: 6054667
Test service: vector

✅ 0 Failed, 2094 Passed, 0 Skipped, 1m 27.61s Wall Time

[github-actions]

Regression Detector Results

Run ID: 614cc8c6-f170-4b53-9f0e-612147edeb54
Baseline: 650d478
Comparison: c14eca8
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
❌	otlp_http_to_blackhole	ingress throughput	-5.36	[-5.51, -5.21]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	datadog_agent_remap_datadog_logs	ingress throughput	+1.59	[+1.50, +1.67]
➖	datadog_agent_remap_blackhole	ingress throughput	+1.31	[+1.20, +1.42]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	+0.89	[+0.78, +0.99]
➖	fluent_elasticsearch	ingress throughput	+0.62	[+0.15, +1.09]
➖	syslog_splunk_hec_logs	ingress throughput	+0.52	[+0.48, +0.57]
➖	http_to_http_acks	ingress throughput	+0.40	[-0.92, +1.72]
➖	syslog_log2metric_humio_metrics	ingress throughput	+0.23	[+0.14, +0.32]
➖	http_to_http_noack	ingress throughput	+0.19	[+0.10, +0.29]
➖	http_to_s3	ingress throughput	+0.13	[-0.15, +0.42]
➖	http_to_http_json	ingress throughput	+0.03	[-0.05, +0.11]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.00	[-0.15, +0.16]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	-0.01	[-0.15, +0.14]
➖	enterprise_http_to_http	ingress throughput	-0.02	[-0.08, +0.05]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.04	[-0.15, +0.08]
➖	http_elasticsearch	ingress throughput	-0.05	[-0.12, +0.02]
➖	syslog_loki	ingress throughput	-0.18	[-0.25, -0.10]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.30	[-0.38, -0.22]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-0.30	[-0.43, -0.18]
➖	splunk_hec_route_s3	ingress throughput	-0.42	[-0.91, +0.07]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	-0.48	[-0.62, -0.33]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-0.55	[-0.69, -0.41]
➖	otlp_grpc_to_blackhole	ingress throughput	-0.93	[-1.02, -0.85]
➖	syslog_humio_logs	ingress throughput	-1.13	[-1.26, -1.01]
➖	file_to_blackhole	egress throughput	-1.47	[-3.97, +1.02]
➖	http_text_to_http_json	ingress throughput	-3.81	[-3.94, -3.69]
➖	socket_to_socket_blackhole	ingress throughput	-4.38	[-4.45, -4.30]
❌	otlp_http_to_blackhole	ingress throughput	-5.36	[-5.51, -5.21]

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: 93f2c366-8bb3-49b0-a28d-090178996b3b
Baseline: 650d478
Comparison: 3fd1843
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
❌	socket_to_socket_blackhole	ingress throughput	-5.26	[-5.31, -5.20]
❌	otlp_http_to_blackhole	ingress throughput	-7.64	[-7.79, -7.48]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	+2.10	[+1.93, +2.27]
➖	file_to_blackhole	egress throughput	+1.70	[-0.77, +4.17]
➖	splunk_hec_route_s3	ingress throughput	+1.48	[+0.97, +1.99]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	+1.13	[+1.05, +1.22]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	+1.13	[+1.03, +1.23]
➖	syslog_humio_logs	ingress throughput	+0.96	[+0.84, +1.07]
➖	syslog_log2metric_humio_metrics	ingress throughput	+0.77	[+0.67, +0.88]
➖	http_elasticsearch	ingress throughput	+0.76	[+0.68, +0.83]
➖	datadog_agent_remap_datadog_logs	ingress throughput	+0.43	[+0.34, +0.52]
➖	datadog_agent_remap_blackhole	ingress throughput	+0.41	[+0.32, +0.51]
➖	http_to_http_noack	ingress throughput	+0.10	[-0.01, +0.21]
➖	http_to_http_json	ingress throughput	+0.03	[-0.05, +0.10]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	-0.00	[-0.16, +0.15]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	-0.00	[-0.14, +0.14]
➖	http_to_http_acks	ingress throughput	-0.02	[-1.33, +1.29]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.04	[-0.15, +0.08]
➖	enterprise_http_to_http	ingress throughput	-0.13	[-0.22, -0.05]
➖	http_to_s3	ingress throughput	-0.22	[-0.51, +0.06]
➖	otlp_grpc_to_blackhole	ingress throughput	-0.46	[-0.55, -0.37]
➖	http_text_to_http_json	ingress throughput	-0.73	[-0.87, -0.59]
➖	syslog_splunk_hec_logs	ingress throughput	-0.78	[-0.84, -0.72]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-0.79	[-0.93, -0.64]
➖	fluent_elasticsearch	ingress throughput	-1.10	[-1.57, -0.63]
➖	syslog_loki	ingress throughput	-1.48	[-1.56, -1.40]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-1.61	[-1.74, -1.48]
❌	socket_to_socket_blackhole	ingress throughput	-5.26	[-5.31, -5.20]
❌	otlp_http_to_blackhole	ingress throughput	-7.64	[-7.79, -7.48]

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: 42dbec5a-a389-4df7-a8e3-4704153492cf
Baseline: 650d478
Comparison: 42b3cbf
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
❌	socket_to_socket_blackhole	ingress throughput	-5.25	[-5.32, -5.17]
❌	otlp_http_to_blackhole	ingress throughput	-6.76	[-6.90, -6.61]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	datadog_agent_remap_blackhole	ingress throughput	+3.43	[+3.28, +3.57]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	+2.35	[+2.22, +2.48]
➖	syslog_log2metric_humio_metrics	ingress throughput	+1.90	[+1.77, +2.04]
➖	datadog_agent_remap_datadog_logs	ingress throughput	+1.57	[+1.49, +1.66]
➖	file_to_blackhole	egress throughput	+1.44	[-1.09, +3.96]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	+1.18	[+1.07, +1.28]
➖	http_to_http_acks	ingress throughput	+1.15	[-0.17, +2.47]
➖	syslog_loki	ingress throughput	+0.37	[+0.31, +0.43]
➖	http_to_http_noack	ingress throughput	+0.19	[+0.10, +0.28]
➖	syslog_humio_logs	ingress throughput	+0.10	[-0.00, +0.20]
➖	fluent_elasticsearch	ingress throughput	+0.09	[-0.37, +0.56]
➖	syslog_splunk_hec_logs	ingress throughput	+0.05	[-0.01, +0.11]
➖	http_to_http_json	ingress throughput	+0.04	[-0.03, +0.12]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	-0.00	[-0.16, +0.15]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	-0.00	[-0.15, +0.14]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-0.03	[-0.17, +0.11]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.06	[-0.17, +0.06]
➖	enterprise_http_to_http	ingress throughput	-0.12	[-0.20, -0.05]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.16	[-0.27, -0.04]
➖	http_elasticsearch	ingress throughput	-0.16	[-0.23, -0.09]
➖	http_to_s3	ingress throughput	-0.18	[-0.46, +0.11]
➖	splunk_hec_route_s3	ingress throughput	-0.85	[-1.34, -0.36]
➖	otlp_grpc_to_blackhole	ingress throughput	-0.87	[-0.96, -0.78]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-0.90	[-1.03, -0.77]
➖	http_text_to_http_json	ingress throughput	-1.84	[-1.96, -1.72]
❌	socket_to_socket_blackhole	ingress throughput	-5.25	[-5.32, -5.17]
❌	otlp_http_to_blackhole	ingress throughput	-6.76	[-6.90, -6.61]

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: a76141a9-7df5-4c53-9e5c-afdf3bdd3f22
Baseline: 13b9147
Comparison: e502a32
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_splunk_hec_logs	ingress throughput	+3.03	[+2.96, +3.11]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	+2.26	[+2.12, +2.40]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	+1.73	[+1.60, +1.87]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	+1.14	[+1.02, +1.25]
➖	syslog_humio_logs	ingress throughput	+0.54	[+0.45, +0.63]
➖	syslog_loki	ingress throughput	+0.35	[+0.28, +0.41]
➖	syslog_log2metric_humio_metrics	ingress throughput	+0.31	[+0.22, +0.41]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	+0.17	[+0.06, +0.28]
➖	http_to_http_noack	ingress throughput	+0.13	[+0.04, +0.23]
➖	http_elasticsearch	ingress throughput	+0.09	[+0.02, +0.16]
➖	http_to_http_json	ingress throughput	+0.04	[-0.03, +0.12]
➖	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]
➖	http_to_http_acks	ingress throughput	-0.01	[-1.32, +1.30]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.04	[-0.16, +0.07]
➖	http_to_s3	ingress throughput	-0.06	[-0.34, +0.23]
➖	enterprise_http_to_http	ingress throughput	-0.11	[-0.19, -0.03]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.12	[-0.19, -0.04]
➖	splunk_hec_route_s3	ingress throughput	-0.49	[-0.97, -0.01]
➖	file_to_blackhole	egress throughput	-0.51	[-2.97, +1.95]
➖	datadog_agent_remap_blackhole	ingress throughput	-0.68	[-0.77, -0.59]
➖	datadog_agent_remap_datadog_logs	ingress throughput	-0.77	[-0.85, -0.70]
➖	socket_to_socket_blackhole	ingress throughput	-1.15	[-1.23, -1.07]
➖	fluent_elasticsearch	ingress throughput	-1.34	[-1.80, -0.88]
➖	otlp_grpc_to_blackhole	ingress throughput	-1.43	[-1.51, -1.34]
➖	http_text_to_http_json	ingress throughput	-1.77	[-1.88, -1.65]
➖	otlp_http_to_blackhole	ingress throughput	-2.58	[-2.74, -2.43]

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

[dependabot]

A newer version of serde_with exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

[github-actions]

Regression Detector Results

Run ID: f00897f8-37da-461e-bb92-704de70be9de
Baseline: 13ac2df
Comparison: 899fd7e
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.08	[+2.93, +3.22]
➖	http_text_to_http_json	ingress throughput	+1.85	[+1.71, +1.99]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	+1.32	[+1.23, +1.42]
➖	syslog_loki	ingress throughput	+1.23	[+1.16, +1.29]
➖	http_to_http_noack	ingress throughput	+0.17	[+0.08, +0.25]
➖	datadog_agent_remap_datadog_logs	ingress throughput	+0.14	[+0.05, +0.23]
➖	http_elasticsearch	ingress throughput	+0.06	[-0.00, +0.13]
➖	fluent_elasticsearch	ingress throughput	+0.06	[-0.41, +0.53]
➖	http_to_http_json	ingress throughput	+0.03	[-0.04, +0.11]
➖	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.14, +0.14]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.06	[-0.17, +0.06]
➖	file_to_blackhole	egress throughput	-0.09	[-2.64, +2.45]
➖	enterprise_http_to_http	ingress throughput	-0.12	[-0.19, -0.04]
➖	http_to_s3	ingress throughput	-0.18	[-0.47, +0.10]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-0.31	[-0.45, -0.16]
➖	splunk_hec_route_s3	ingress throughput	-0.38	[-0.88, +0.13]
➖	syslog_splunk_hec_logs	ingress throughput	-0.38	[-0.45, -0.32]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	-0.51	[-0.60, -0.42]
➖	otlp_http_to_blackhole	ingress throughput	-0.54	[-0.68, -0.40]
➖	datadog_agent_remap_blackhole	ingress throughput	-0.65	[-0.74, -0.55]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.91	[-0.98, -0.83]
➖	otlp_grpc_to_blackhole	ingress throughput	-1.04	[-1.13, -0.96]
➖	socket_to_socket_blackhole	ingress throughput	-1.51	[-1.59, -1.43]
➖	syslog_humio_logs	ingress throughput	-1.52	[-1.62, -1.41]
➖	http_to_http_acks	ingress throughput	-1.85	[-3.15, -0.55]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-2.53	[-2.66, -2.40]

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

[jszwedko]

@dependabot recreate

[dependabot]

Superseded by #19800.