chore(deps): Bump async-compression from 0.4.1 to 0.4.2

[dependabot]

Bumps async-compression from 0.4.1 to 0.4.2.

Release notes

Sourced from async-compression's releases.

async-compression: v0.4.2

• Add top-level brotli module containing stable brotli crate wrapper types.
• Add BrotliEncoder::with_quality_and_params() constructors.
• Add Deflate64Decoder behind new crate feature deflate64.

Changelog

Sourced from async-compression's changelog.

0.4.2

• Add top-level brotli module containing stable brotli crate wrapper types.
• Add BrotliEncoder::with_quality_and_params() constructors.
• Add Deflate64Decoder behind new crate feature deflate64.

Commits

• 8273067 Merge pull request #243 from Nullus157/rel-042
• cb0a54f chore(async-compression): prepare release 0.4.2
• 29a411b Merge pull request #242 from Nullus157/brotli-params
• b698b1a feat: re-add Copy derive to brotli::EncoderParams
• ee2acc1 chore: remove EncoderParams Copy derive
• 6150080 docs: update changelog
• 14d916a feat: add brotli module
• 1cb4371 refactor: move zstd module to file
• 8af8b96 Merge pull request #241 from Nullus157/update-deny
• f021120 update deny config
• 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 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)

[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 vector-project ready!

Name	Link
🔨 Latest commit	3ce492b
🔍 Latest deploy log	https://app.netlify.com/sites/vector-project/deploys/64ed6a0a4d750a000811cc9a
😎 Deploy Preview	https://deploy-preview-18417--vector-project.netlify.app
📱 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.

[netlify]

✅ Deploy Preview for vrl-playground canceled.

Name	Link
🔨 Latest commit	3ce492b
🔍 Latest deploy log	https://app.netlify.com/sites/vrl-playground/deploys/64ed6a0ae98781000848a8fa

[github-actions]

Regression Detector Results

Run ID: 64841c63-cab4-4649-827d-d7293ae867a6
Baseline: e39d9b3
Comparison: ff8e61e
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
http_to_http_noack	ingress throughput	-9.06	100.00%

Fine details of change detection per experiment.

experiment	goal	Δ mean %	Δ mean % CI	confidence
enterprise_http_to_http	ingress throughput	+2.18	[+2.04, +2.31]	100.00%
splunk_hec_route_s3	ingress throughput	+1.79	[+1.38, +2.21]	100.00%
http_to_http_acks	ingress throughput	+0.58	[+0.46, +0.71]	100.00%
splunk_hec_to_splunk_hec_logs_noack	ingress throughput	+0.55	[+0.44, +0.66]	100.00%
splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.05	[-0.07, +0.16]	40.14%
splunk_hec_indexer_ack_blackhole	ingress throughput	+0.01	[-0.12, +0.14]	9.95%
http_to_http_json	ingress throughput	-0.00	[-0.04, +0.04]	0.33%
http_text_to_http_json	ingress throughput	-0.11	[-0.19, -0.03]	92.37%
datadog_agent_remap_blackhole	ingress throughput	-0.21	[-0.30, -0.11]	99.39%
syslog_log2metric_humio_metrics	ingress throughput	-0.28	[-0.40, -0.15]	99.57%
http_to_s3	ingress throughput	-0.41	[-0.62, -0.21]	99.04%
file_to_blackhole	egress throughput	-0.69	[-1.61, +0.23]	66.25%
syslog_splunk_hec_logs	ingress throughput	-0.73	[-0.79, -0.67]	100.00%
socket_to_socket_blackhole	ingress throughput	-0.91	[-0.94, -0.89]	100.00%
syslog_loki	ingress throughput	-1.00	[-1.06, -0.94]	100.00%
fluent_elasticsearch	ingress throughput	-1.11	[-1.35, -0.87]	100.00%
datadog_agent_remap_datadog_logs_acks	ingress throughput	-1.32	[-1.45, -1.20]	100.00%
otlp_grpc_to_blackhole	ingress throughput	-1.54	[-1.62, -1.46]	100.00%
datadog_agent_remap_datadog_logs	ingress throughput	-1.64	[-1.80, -1.48]	100.00%
syslog_log2metric_splunk_hec_metrics	ingress throughput	-1.75	[-1.87, -1.63]	100.00%
datadog_agent_remap_blackhole_acks	ingress throughput	-1.92	[-2.00, -1.83]	100.00%
syslog_humio_logs	ingress throughput	-1.96	[-2.06, -1.86]	100.00%
otlp_http_to_blackhole	ingress throughput	-2.71	[-2.89, -2.54]	100.00%
syslog_regex_logs2metric_ddmetrics	ingress throughput	-5.52	[-5.81, -5.23]	100.00%
http_to_http_noack	ingress throughput	-9.06	[-9.52, -8.61]	100.00%

[github-actions]

Regression Detector Results

Run ID: 9307ea8e-62d0-4ecd-a9ae-a08501906c7e
Baseline: c4c47c9
Comparison: f99e9a5
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
otlp_http_to_blackhole	ingress throughput	+3.54	[+3.36, +3.71]	100.00%
syslog_humio_logs	ingress throughput	+3.27	[+3.17, +3.37]	100.00%
socket_to_socket_blackhole	ingress throughput	+2.81	[+2.77, +2.85]	100.00%
http_to_http_acks	ingress throughput	+2.01	[+1.88, +2.14]	100.00%
datadog_agent_remap_datadog_logs_acks	ingress throughput	+1.85	[+1.73, +1.97]	100.00%
syslog_log2metric_splunk_hec_metrics	ingress throughput	+1.45	[+1.29, +1.60]	100.00%
datadog_agent_remap_blackhole	ingress throughput	+1.24	[+1.15, +1.33]	100.00%
otlp_grpc_to_blackhole	ingress throughput	+0.81	[+0.72, +0.89]	100.00%
splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.28	[+0.17, +0.40]	99.86%
syslog_loki	ingress throughput	+0.18	[+0.12, +0.23]	99.99%
fluent_elasticsearch	ingress throughput	+0.13	[-0.11, +0.37]	50.59%
http_to_s3	ingress throughput	+0.12	[-0.09, +0.33]	54.22%
splunk_hec_route_s3	ingress throughput	+0.02	[-0.41, +0.46]	5.54%
http_to_http_json	ingress throughput	+0.00	[-0.04, +0.04]	1.45%
splunk_hec_indexer_ack_blackhole	ingress throughput	-0.00	[-0.13, +0.12]	3.71%
splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.01	[-0.12, +0.10]	9.79%
syslog_splunk_hec_logs	ingress throughput	-0.09	[-0.16, -0.03]	93.69%
http_to_http_noack	ingress throughput	-0.10	[-0.23, +0.04]	64.49%
enterprise_http_to_http	ingress throughput	-0.28	[-0.41, -0.15]	99.35%
datadog_agent_remap_datadog_logs	ingress throughput	-0.29	[-0.40, -0.17]	99.80%
syslog_log2metric_humio_metrics	ingress throughput	-0.32	[-0.44, -0.21]	99.96%
http_text_to_http_json	ingress throughput	-1.17	[-1.26, -1.09]	100.00%
file_to_blackhole	egress throughput	-1.41	[-2.31, -0.51]	95.58%
datadog_agent_remap_blackhole_acks	ingress throughput	-1.60	[-1.69, -1.51]	100.00%
syslog_regex_logs2metric_ddmetrics	ingress throughput	-2.87	[-3.18, -2.55]	100.00%

[github-actions]

Regression Detector Results

Run ID: a8d7ab29-6962-49e7-8448-384c926fb30d
Baseline: 15792f6
Comparison: 8639655
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	+3.75	[+3.44, +4.06]	100.00%
http_to_http_noack	ingress throughput	+2.71	[+2.58, +2.85]	100.00%
syslog_log2metric_splunk_hec_metrics	ingress throughput	+2.18	[+2.05, +2.31]	100.00%
datadog_agent_remap_blackhole	ingress throughput	+1.58	[+1.50, +1.67]	100.00%
http_to_http_acks	ingress throughput	+1.08	[+0.92, +1.24]	100.00%
file_to_blackhole	egress throughput	+1.04	[+0.08, +2.00]	83.59%
enterprise_http_to_http	ingress throughput	+1.00	[+0.88, +1.13]	100.00%
syslog_loki	ingress throughput	+0.94	[+0.89, +1.00]	100.00%
socket_to_socket_blackhole	ingress throughput	+0.93	[+0.90, +0.96]	100.00%
http_text_to_http_json	ingress throughput	+0.90	[+0.80, +1.00]	100.00%
http_to_s3	ingress throughput	+0.85	[+0.64, +1.06]	100.00%
syslog_splunk_hec_logs	ingress throughput	+0.67	[+0.61, +0.74]	100.00%
fluent_elasticsearch	ingress throughput	+0.48	[+0.23, +0.72]	98.70%
splunk_hec_to_splunk_hec_logs_noack	ingress throughput	+0.00	[-0.10, +0.11]	2.86%
http_to_http_json	ingress throughput	-0.00	[-0.04, +0.04]	1.12%
splunk_hec_indexer_ack_blackhole	ingress throughput	-0.00	[-0.13, +0.13]	1.28%
datadog_agent_remap_datadog_logs	ingress throughput	-0.04	[-0.15, +0.07]	36.03%
splunk_hec_to_splunk_hec_logs_acks	ingress throughput	-0.11	[-0.22, -0.00]	80.04%
splunk_hec_route_s3	ingress throughput	-0.36	[-0.78, +0.06]	73.24%
datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.56	[-0.69, -0.43]	100.00%
datadog_agent_remap_blackhole_acks	ingress throughput	-0.61	[-0.71, -0.51]	100.00%
otlp_grpc_to_blackhole	ingress throughput	-0.88	[-0.97, -0.79]	100.00%
otlp_http_to_blackhole	ingress throughput	-0.98	[-1.15, -0.81]	100.00%
syslog_humio_logs	ingress throughput	-2.31	[-2.40, -2.22]	100.00%
syslog_log2metric_humio_metrics	ingress throughput	-3.21	[-3.32, -3.10]	100.00%