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

[dependabot]

Bumps the tonic group with 2 updates: tonic and tonic-build.

Updates tonic from 0.10.1 to 0.10.2

Changelog

Sourced from tonic's changelog.

0.10.2 (2023-09-28)

Bug Fixes

• web: Client decoding incomplete buffer bug (#1540) (83e363a)

Commits

• b3fca19 chore: Prepare 0.10.2 release (#1541)
• 83e363a fix(web): Client decoding incomplete buffer bug (#1540)
• See full diff in compare view

Updates tonic-build from 0.10.1 to 0.10.2

Changelog

Sourced from tonic-build's changelog.

0.10.2 (2023-09-28)

Bug Fixes

• web: Client decoding incomplete buffer bug (#1540) (83e363a)

Commits

• b3fca19 chore: Prepare 0.10.2 release (#1541)
• 83e363a fix(web): Client decoding incomplete buffer bug (#1540)
• 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

[bits-bot]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[netlify]

✅ Deploy Preview for vrl-playground canceled.

Name	Link
🔨 Latest commit	a3f80fb
🔍 Latest deploy log	https://app.netlify.com/sites/vrl-playground/deploys/65174d63584ba0000809c538

[netlify]

✅ Deploy Preview for vector-project ready!

Name	Link
🔨 Latest commit	a3f80fb
🔍 Latest deploy log	https://app.netlify.com/sites/vector-project/deploys/65174d638aab58000768a4d7
😎 Deploy Preview	https://deploy-preview-18714--vector-project.netlify.app/docs/reference/configuration/unit-tests
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

Regression Detector Results

Run ID: d512483a-a988-4ad8-8f6f-56561e4c892d
Baseline: 089630b
Comparison: bf56982
Total vector CPUs: 7

Explanation

A regression test is an integrated performance test for vector in a repeatable rig, with varying configuration for vector. What follows is a statistical summary of a brief vector run for each configuration across SHAs given above. The goal of these tests are to determine quickly if vector performance is changed and to what degree by a pull request.

Because a target's optimization goal performance in each experiment will vary somewhat each time it is run, we can only estimate mean differences in optimization goal relative to the baseline target. We express these differences as a percentage change relative to the baseline target, denoted "Δ mean %". These estimates are made to a precision that balances accuracy and cost control. We represent this precision as a 90.00% confidence interval denoted "Δ mean % CI": there is a 90.00% chance that the true value of "Δ mean %" is in that interval.

We decide whether a change in performance is a "regression" -- a change worth investigating further -- if both of the following two criteria are true:

1. The estimated |Δ mean %| ≥ 5.00%. This criterion intends to answer the question "Does the estimated change in mean optimization goal performance have a meaningful impact on your customers?". We assume that when |Δ mean %| < 5.00%, the impact on your customers is not meaningful. We also assume that a performance change in optimization goal is worth investigating whether it is an increase or decrease, so long as the magnitude of the change is sufficiently large.

2. Zero is not in the 90.00% confidence interval "Δ mean % CI" about "Δ mean %". This statement is equivalent to saying that there is at least a 90.00% chance that the mean difference in optimization goal is not zero. This criterion intends to answer the question, "Is there a statistically significant difference in mean optimization goal performance?". It also means there is no more than a 10.00% chance this criterion reports a statistically significant difference when the true difference in mean optimization goal is zero -- a "false positive". We assume you are willing to accept a 10.00% chance of inaccurately detecting a change in performance when no true difference exists.

The table below, if present, lists those experiments that have experienced a statistically significant change in mean optimization goal performance between baseline and comparison SHAs with 90.00% confidence OR have been detected as newly erratic. Negative values of "Δ mean %" mean that baseline is faster, whereas positive values of "Δ mean %" mean that comparison is faster. Results that do not exhibit more than a ±5.00% change in their mean optimization goal are discarded. An experiment is erratic if its coefficient of variation is greater than 0.1. The abbreviated table will be omitted if no interesting change is observed.

Changes in experiment optimization goals with confidence ≥ 90.00% and |Δ mean %| ≥ 5.00%:

experiment	goal	Δ mean %	confidence
syslog_log2metric_humio_metrics	ingress throughput	-5.24	100.00%

Fine details of change detection per experiment.

experiment	goal	Δ mean %	Δ mean % CI	confidence
syslog_regex_logs2metric_ddmetrics	ingress throughput	+3.56	[+3.05, +4.07]	100.00%
syslog_log2metric_splunk_hec_metrics	ingress throughput	+3.45	[+3.28, +3.63]	100.00%
syslog_humio_logs	ingress throughput	+3.43	[+3.30, +3.56]	100.00%
syslog_loki	ingress throughput	+2.84	[+2.79, +2.90]	100.00%
file_to_blackhole	egress throughput	+2.34	[+1.13, +3.56]	99.85%
http_text_to_http_json	ingress throughput	+2.13	[+1.97, +2.28]	100.00%
syslog_splunk_hec_logs	ingress throughput	+2.08	[+1.97, +2.20]	100.00%
enterprise_http_to_http	ingress throughput	+1.57	[+1.41, +1.72]	100.00%
splunk_hec_route_s3	ingress throughput	+1.33	[+0.80, +1.86]	100.00%
datadog_agent_remap_datadog_logs	ingress throughput	+0.89	[+0.72, +1.05]	100.00%
datadog_agent_remap_datadog_logs_acks	ingress throughput	+0.25	[+0.09, +0.40]	99.19%
http_to_s3	ingress throughput	+0.04	[-0.25, +0.32]	17.03%
splunk_hec_indexer_ack_blackhole	ingress throughput	+0.01	[-0.15, +0.18]	10.74%
http_to_http_json	ingress throughput	-0.00	[-0.05, +0.05]	0.28%
splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.00	[-0.15, +0.14]	0.90%
splunk_hec_to_splunk_hec_logs_acks	ingress throughput	-0.03	[-0.19, +0.14]	19.95%
datadog_agent_remap_blackhole_acks	ingress throughput	-0.10	[-0.22, +0.01]	85.51%
otlp_grpc_to_blackhole	ingress throughput	-0.69	[-0.81, -0.56]	100.00%
http_to_http_noack	ingress throughput	-0.88	[-1.05, -0.70]	100.00%
datadog_agent_remap_blackhole	ingress throughput	-1.17	[-1.26, -1.09]	100.00%
otlp_http_to_blackhole	ingress throughput	-1.56	[-1.73, -1.39]	100.00%
http_to_http_acks	ingress throughput	-2.75	[-2.92, -2.58]	100.00%
socket_to_socket_blackhole	ingress throughput	-2.80	[-2.86, -2.74]	100.00%
fluent_elasticsearch	ingress throughput	-3.99	[-4.30, -3.69]	100.00%
syslog_log2metric_humio_metrics	ingress throughput	-5.24	[-5.40, -5.07]	100.00%

[github-actions]

Regression Detector Results

Run ID: 403c51ae-89a8-4751-b26c-1a7da68b5a54
Baseline: 18f07a0
Comparison: 1cafffe
Total vector CPUs: 7

Explanation

A regression test is an integrated performance test for vector in a repeatable rig, with varying configuration for vector. What follows is a statistical summary of a brief vector run for each configuration across SHAs given above. The goal of these tests are to determine quickly if vector performance is changed and to what degree by a pull request.

Because a target's optimization goal performance in each experiment will vary somewhat each time it is run, we can only estimate mean differences in optimization goal relative to the baseline target. We express these differences as a percentage change relative to the baseline target, denoted "Δ mean %". These estimates are made to a precision that balances accuracy and cost control. We represent this precision as a 90.00% confidence interval denoted "Δ mean % CI": there is a 90.00% chance that the true value of "Δ mean %" is in that interval.

We decide whether a change in performance is a "regression" -- a change worth investigating further -- if both of the following two criteria are true:

1. The estimated |Δ mean %| ≥ 5.00%. This criterion intends to answer the question "Does the estimated change in mean optimization goal performance have a meaningful impact on your customers?". We assume that when |Δ mean %| < 5.00%, the impact on your customers is not meaningful. We also assume that a performance change in optimization goal is worth investigating whether it is an increase or decrease, so long as the magnitude of the change is sufficiently large.

2. Zero is not in the 90.00% confidence interval "Δ mean % CI" about "Δ mean %". This statement is equivalent to saying that there is at least a 90.00% chance that the mean difference in optimization goal is not zero. This criterion intends to answer the question, "Is there a statistically significant difference in mean optimization goal performance?". It also means there is no more than a 10.00% chance this criterion reports a statistically significant difference when the true difference in mean optimization goal is zero -- a "false positive". We assume you are willing to accept a 10.00% chance of inaccurately detecting a change in performance when no true difference exists.

The table below, if present, lists those experiments that have experienced a statistically significant change in mean optimization goal performance between baseline and comparison SHAs with 90.00% confidence OR have been detected as newly erratic. Negative values of "Δ mean %" mean that baseline is faster, whereas positive values of "Δ mean %" mean that comparison is faster. Results that do not exhibit more than a ±5.00% change in their mean optimization goal are discarded. An experiment is erratic if its coefficient of variation is greater than 0.1. The abbreviated table will be omitted if no interesting change is observed.

No interesting changes in experiment optimization goals with confidence ≥ 90.00% and |Δ mean %| ≥ 5.00%.

Fine details of change detection per experiment.

experiment	goal	Δ mean %	Δ mean % CI	confidence
syslog_log2metric_humio_metrics	ingress throughput	+3.51	[+3.30, +3.71]	100.00%
syslog_loki	ingress throughput	+2.14	[+2.05, +2.22]	100.00%
splunk_hec_route_s3	ingress throughput	+1.58	[+1.05, +2.11]	100.00%
enterprise_http_to_http	ingress throughput	+1.43	[+1.26, +1.60]	100.00%
http_to_http_noack	ingress throughput	+1.24	[+1.07, +1.40]	100.00%
datadog_agent_remap_blackhole_acks	ingress throughput	+0.97	[+0.84, +1.09]	100.00%
syslog_splunk_hec_logs	ingress throughput	+0.67	[+0.57, +0.77]	100.00%
syslog_log2metric_splunk_hec_metrics	ingress throughput	+0.61	[+0.43, +0.80]	100.00%
syslog_humio_logs	ingress throughput	+0.58	[+0.47, +0.68]	100.00%
otlp_grpc_to_blackhole	ingress throughput	+0.57	[+0.47, +0.67]	100.00%
file_to_blackhole	egress throughput	+0.51	[-0.58, +1.61]	55.84%
http_to_s3	ingress throughput	+0.32	[+0.03, +0.60]	93.13%
splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.02	[-0.14, +0.19]	17.86%
http_to_http_acks	ingress throughput	+0.00	[-0.15, +0.16]	0.71%
http_to_http_json	ingress throughput	-0.01	[-0.06, +0.05]	13.91%
splunk_hec_indexer_ack_blackhole	ingress throughput	-0.01	[-0.17, +0.16]	5.05%
splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.01	[-0.15, +0.14]	8.13%
datadog_agent_remap_blackhole	ingress throughput	-0.08	[-0.20, +0.04]	71.98%
datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.17	[-0.35, +0.01]	87.03%
datadog_agent_remap_datadog_logs	ingress throughput	-0.32	[-0.44, -0.19]	100.00%
fluent_elasticsearch	ingress throughput	-1.32	[-1.63, -1.02]	100.00%
syslog_regex_logs2metric_ddmetrics	ingress throughput	-1.62	[-2.03, -1.21]	100.00%
http_text_to_http_json	ingress throughput	-2.14	[-2.29, -2.00]	100.00%
socket_to_socket_blackhole	ingress throughput	-3.09	[-3.17, -3.01]	100.00%
otlp_http_to_blackhole	ingress throughput	-4.81	[-4.99, -4.64]	100.00%

[github-actions]

Regression Detector Results

Run ID: 08fa539d-8295-49b1-bd4f-7a368e5add53
Baseline: 65643da
Comparison: c95df7c
Total vector CPUs: 7

Explanation

A regression test is an integrated performance test for vector in a repeatable rig, with varying configuration for vector. What follows is a statistical summary of a brief vector run for each configuration across SHAs given above. The goal of these tests are to determine quickly if vector performance is changed and to what degree by a pull request.

Because a target's optimization goal performance in each experiment will vary somewhat each time it is run, we can only estimate mean differences in optimization goal relative to the baseline target. We express these differences as a percentage change relative to the baseline target, denoted "Δ mean %". These estimates are made to a precision that balances accuracy and cost control. We represent this precision as a 90.00% confidence interval denoted "Δ mean % CI": there is a 90.00% chance that the true value of "Δ mean %" is in that interval.

We decide whether a change in performance is a "regression" -- a change worth investigating further -- if both of the following two criteria are true:

1. The estimated |Δ mean %| ≥ 5.00%. This criterion intends to answer the question "Does the estimated change in mean optimization goal performance have a meaningful impact on your customers?". We assume that when |Δ mean %| < 5.00%, the impact on your customers is not meaningful. We also assume that a performance change in optimization goal is worth investigating whether it is an increase or decrease, so long as the magnitude of the change is sufficiently large.

2. Zero is not in the 90.00% confidence interval "Δ mean % CI" about "Δ mean %". This statement is equivalent to saying that there is at least a 90.00% chance that the mean difference in optimization goal is not zero. This criterion intends to answer the question, "Is there a statistically significant difference in mean optimization goal performance?". It also means there is no more than a 10.00% chance this criterion reports a statistically significant difference when the true difference in mean optimization goal is zero -- a "false positive". We assume you are willing to accept a 10.00% chance of inaccurately detecting a change in performance when no true difference exists.

The table below, if present, lists those experiments that have experienced a statistically significant change in mean optimization goal performance between baseline and comparison SHAs with 90.00% confidence OR have been detected as newly erratic. Negative values of "Δ mean %" mean that baseline is faster, whereas positive values of "Δ mean %" mean that comparison is faster. Results that do not exhibit more than a ±5.00% change in their mean optimization goal are discarded. An experiment is erratic if its coefficient of variation is greater than 0.1. The abbreviated table will be omitted if no interesting change is observed.

No interesting changes in experiment optimization goals with confidence ≥ 90.00% and |Δ mean %| ≥ 5.00%.

Fine details of change detection per experiment.

experiment	goal	Δ mean %	Δ mean % CI	confidence
syslog_regex_logs2metric_ddmetrics	ingress throughput	+7.03	[+6.54, +7.52]	100.00%
otlp_http_to_blackhole	ingress throughput	+4.09	[+3.91, +4.26]	100.00%
socket_to_socket_blackhole	ingress throughput	+2.63	[+2.54, +2.73]	100.00%
syslog_log2metric_humio_metrics	ingress throughput	+1.88	[+1.72, +2.05]	100.00%
datadog_agent_remap_blackhole	ingress throughput	+1.31	[+1.20, +1.43]	100.00%
datadog_agent_remap_datadog_logs_acks	ingress throughput	+1.01	[+0.86, +1.16]	100.00%
syslog_splunk_hec_logs	ingress throughput	+0.58	[+0.51, +0.65]	100.00%
datadog_agent_remap_datadog_logs	ingress throughput	+0.57	[+0.41, +0.73]	100.00%
otlp_grpc_to_blackhole	ingress throughput	+0.56	[+0.43, +0.68]	100.00%
syslog_loki	ingress throughput	+0.55	[+0.46, +0.63]	100.00%
http_to_http_noack	ingress throughput	+0.43	[+0.27, +0.60]	100.00%
enterprise_http_to_http	ingress throughput	+0.41	[+0.23, +0.59]	99.98%
syslog_log2metric_splunk_hec_metrics	ingress throughput	+0.34	[+0.15, +0.52]	99.78%
splunk_hec_route_s3	ingress throughput	+0.18	[-0.36, +0.71]	41.85%
http_text_to_http_json	ingress throughput	+0.02	[-0.09, +0.13]	22.53%
splunk_hec_to_splunk_hec_logs_noack	ingress throughput	+0.00	[-0.13, +0.14]	3.46%
http_to_http_json	ingress throughput	+0.00	[-0.05, +0.05]	4.78%
splunk_hec_indexer_ack_blackhole	ingress throughput	+0.00	[-0.16, +0.17]	1.40%
splunk_hec_to_splunk_hec_logs_acks	ingress throughput	-0.02	[-0.18, +0.14]	15.28%
datadog_agent_remap_blackhole_acks	ingress throughput	-0.34	[-0.46, -0.21]	100.00%
http_to_s3	ingress throughput	-1.05	[-1.34, -0.77]	100.00%
http_to_http_acks	ingress throughput	-1.15	[-1.29, -1.00]	100.00%
fluent_elasticsearch	ingress throughput	-1.22	[-1.53, -0.92]	100.00%
file_to_blackhole	egress throughput	-1.55	[-2.76, -0.34]	96.49%
syslog_humio_logs	ingress throughput	-2.15	[-2.28, -2.02]	100.00%