chore(deps): Bump proc-macro2 from 1.0.81 to 1.0.82

[dependabot]

Bumps proc-macro2 from 1.0.81 to 1.0.82.

Release notes

Sourced from proc-macro2's releases.

1.0.82

• Resolve unexpected_cfgs warning (#456)

Commits

• 8dc63f3 Release 1.0.82
• 790cb41 Merge pull request #457 from dtolnay/defaultfeatures
• 2ebe711 Fix use of deprecated default_features in Cargo.toml
• a720819 Delete unused nightly cfg
• 37c5d18 Merge pull request #456 from dtolnay/checkcfg
• 5e02f52 Suppress unknown_lints warning on old rustc
• 2660d30 Resolve unexpected_cfgs warning
• 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 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]

Regression Detector Results

Run ID: 1d762a67-4310-4981-ba15-47f7f664f1c9
Baseline: 75585d6
Comparison: 2aaf209
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_humio_logs	ingress throughput	+1.55	[+1.41, +1.69]
➖	http_to_http_acks	ingress throughput	+0.88	[-0.49, +2.25]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	+0.36	[+0.28, +0.44]
➖	http_to_http_noack	ingress throughput	+0.23	[+0.14, +0.33]
➖	datadog_agent_remap_blackhole	ingress throughput	+0.06	[-0.06, +0.18]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.00	[-0.14, +0.14]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	-0.00	[-0.15, +0.14]
➖	http_to_http_json	ingress throughput	-0.00	[-0.08, +0.07]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.06	[-0.17, +0.05]
➖	enterprise_http_to_http	ingress throughput	-0.10	[-0.16, -0.04]
➖	splunk_hec_route_s3	ingress throughput	-0.22	[-0.70, +0.27]
➖	file_to_blackhole	egress throughput	-0.26	[-2.71, +2.19]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	-0.28	[-0.38, -0.17]
➖	socket_to_socket_blackhole	ingress throughput	-0.48	[-0.57, -0.39]
➖	http_to_s3	ingress throughput	-0.59	[-0.87, -0.31]
➖	otlp_http_to_blackhole	ingress throughput	-0.74	[-0.87, -0.61]
➖	fluent_elasticsearch	ingress throughput	-0.88	[-1.36, -0.40]
➖	http_text_to_http_json	ingress throughput	-0.97	[-1.10, -0.84]
➖	otlp_grpc_to_blackhole	ingress throughput	-0.97	[-1.06, -0.88]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	-1.32	[-1.50, -1.14]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-1.48	[-1.62, -1.34]
➖	syslog_loki	ingress throughput	-1.74	[-1.83, -1.66]
➖	syslog_splunk_hec_logs	ingress throughput	-2.06	[-2.15, -1.98]
➖	http_elasticsearch	ingress throughput	-2.07	[-2.15, -1.98]
➖	datadog_agent_remap_datadog_logs	ingress throughput	-2.12	[-2.24, -2.00]
➖	syslog_log2metric_humio_metrics	ingress throughput	-2.48	[-2.61, -2.35]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-3.08	[-3.25, -2.92]

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: 29ec940c-80fb-49b1-bb37-32c18d7df648
Baseline: a7b9f9e
Comparison: 9a02cb5
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
➖	socket_to_socket_blackhole	ingress throughput	+3.62	[+3.53, +3.72]
➖	otlp_http_to_blackhole	ingress throughput	+1.90	[+1.78, +2.02]
➖	http_elasticsearch	ingress throughput	+1.58	[+1.51, +1.65]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	+1.53	[+1.41, +1.64]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	+0.71	[+0.54, +0.87]
➖	syslog_humio_logs	ingress throughput	+0.60	[+0.48, +0.72]
➖	fluent_elasticsearch	ingress throughput	+0.43	[-0.05, +0.91]
➖	file_to_blackhole	egress throughput	+0.33	[-2.15, +2.81]
➖	splunk_hec_route_s3	ingress throughput	+0.26	[-0.19, +0.71]
➖	datadog_agent_remap_datadog_logs	ingress throughput	+0.23	[+0.12, +0.34]
➖	http_to_http_noack	ingress throughput	+0.16	[+0.07, +0.25]
➖	syslog_splunk_hec_logs	ingress throughput	+0.12	[+0.06, +0.18]
➖	http_to_http_json	ingress throughput	+0.03	[-0.05, +0.10]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	+0.00	[-0.14, +0.14]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	-0.00	[-0.14, +0.14]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.01	[-0.13, +0.10]
➖	enterprise_http_to_http	ingress throughput	-0.07	[-0.15, -0.00]
➖	otlp_grpc_to_blackhole	ingress throughput	-0.20	[-0.29, -0.11]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	-0.32	[-0.47, -0.16]
➖	syslog_loki	ingress throughput	-0.35	[-0.42, -0.27]
➖	http_to_s3	ingress throughput	-0.42	[-0.70, -0.14]
➖	http_to_http_acks	ingress throughput	-0.58	[-1.94, +0.79]
➖	datadog_agent_remap_blackhole	ingress throughput	-0.63	[-0.74, -0.52]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.95	[-1.05, -0.86]
➖	http_text_to_http_json	ingress throughput	-1.14	[-1.28, -1.00]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-1.19	[-1.32, -1.06]
➖	syslog_log2metric_humio_metrics	ingress throughput	-4.31	[-4.46, -4.16]

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]

Dependabot attempted to update this pull request, but because the branch dependabot/cargo/proc-macro2-1.0.82 is protected it was unable to do so.

[github-actions]

Regression Detector Results

Run ID: 11a93189-0b6f-47cd-b024-f6c164a8754e
Baseline: cdda013
Comparison: f5f16cc
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
➖	socket_to_socket_blackhole	ingress throughput	+2.50	[+2.42, +2.58]
➖	syslog_humio_logs	ingress throughput	+2.44	[+2.28, +2.61]
➖	datadog_agent_remap_datadog_logs	ingress throughput	+1.44	[+1.32, +1.55]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	+1.27	[+1.18, +1.36]
➖	file_to_blackhole	egress throughput	+1.06	[-1.44, +3.55]
➖	fluent_elasticsearch	ingress throughput	+0.81	[+0.32, +1.30]
➖	http_text_to_http_json	ingress throughput	+0.50	[+0.38, +0.62]
➖	http_to_http_acks	ingress throughput	+0.17	[-1.19, +1.52]
➖	http_to_http_noack	ingress throughput	+0.12	[+0.02, +0.23]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	+0.00	[-0.14, +0.15]
➖	http_to_http_json	ingress throughput	+0.00	[-0.07, +0.07]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.00	[-0.14, +0.14]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.02	[-0.13, +0.09]
➖	http_to_s3	ingress throughput	-0.02	[-0.30, +0.26]
➖	enterprise_http_to_http	ingress throughput	-0.04	[-0.12, +0.03]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-0.14	[-0.28, -0.00]
➖	otlp_http_to_blackhole	ingress throughput	-0.16	[-0.32, -0.01]
➖	datadog_agent_remap_blackhole	ingress throughput	-0.45	[-0.60, -0.31]
➖	otlp_grpc_to_blackhole	ingress throughput	-0.48	[-0.57, -0.39]
➖	syslog_log2metric_humio_metrics	ingress throughput	-0.84	[-0.98, -0.71]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-0.97	[-1.12, -0.82]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	-1.20	[-1.34, -1.05]
➖	syslog_splunk_hec_logs	ingress throughput	-1.64	[-1.74, -1.54]
➖	syslog_loki	ingress throughput	-1.72	[-1.77, -1.68]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	-2.02	[-2.13, -1.90]
➖	http_elasticsearch	ingress throughput	-2.84	[-3.07, -2.60]
➖	splunk_hec_route_s3	ingress throughput	-3.20	[-3.66, -2.73]

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