chore(deps): Bump regex from 1.8.3 to 1.8.4

[dependabot]

Bumps regex from 1.8.3 to 1.8.4.

Changelog

Sourced from regex's changelog.

1.8.4 (2023-06-05)

This is a patch release that fixes a bug where (?-u:\B) was allowed in Unicode regexes, despite the fact that the current matching engines can report match offsets between the code units of a single UTF-8 encoded codepoint. That in turn means that match offsets that split a codepoint could be reported, which in turn results in panicking when one uses them to slice a &str.

This bug occurred in the transition to regex 1.8 because the underlying syntactical error that prevented this regex from compiling was intentionally removed. That's because (?-u:\B) will be permitted in Unicode regexes in regex 1.9, but the matching engines will guarantee to never report match offsets that split a codepoint. When the underlying syntactical error was removed, no code was added to ensure that (?-u:\B) didn't compile in the regex 1.8 transition release. This release, regex 1.8.4, adds that code such that Regex::new(r"(?-u:\B)") returns to the regex <1.8 behavior of not compiling. (A bytes::Regex can still of course compile it.)

Bug fixes:

• [BUG #1006](rust-lang/regex#1006): Fix a bug where (?-u:\B) was allowed in Unicode regexes, and in turn could lead to match offsets that split a codepoint in &str.

Commits

• 5a34a39 1.8.4
• 407f6d3 changelog: 1.8.4
• b2ca9c1 compile: make Regex::new(r"(?-u:\B)") fail again
• 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 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	ad55d39
🔍 Latest deploy log	https://app.netlify.com/sites/vector-project/deploys/647e041de34c1400089f01ac
😎 Deploy Preview	https://deploy-preview-17601--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 settings.

[netlify]

✅ Deploy Preview for vrl-playground ready!

Name	Link
🔨 Latest commit	ad55d39
🔍 Latest deploy log	https://app.netlify.com/sites/vrl-playground/deploys/647e041d1af4220008a58de7
😎 Deploy Preview	https://deploy-preview-17601--vrl-playground.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 settings.

[neuronull]

@dependabot rebase

[dependabot]

Looks like this PR is already up-to-date with master! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[github-actions]

Regression Detector Results

Run ID: 06ce2a63-8aa6-461b-ba77-ee66d2e8562a
Baseline: 66c1a16
Comparison: 00dae5a
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	+4.08	[+3.84, +4.31]	100.00%
otlp_http_to_blackhole	ingress throughput	+2.67	[+2.48, +2.86]	100.00%
datadog_agent_remap_blackhole	ingress throughput	+1.65	[+1.56, +1.75]	100.00%
datadog_agent_remap_datadog_logs	ingress throughput	+0.88	[+0.76, +0.99]	100.00%
http_text_to_http_json	ingress throughput	+0.87	[+0.80, +0.93]	100.00%
syslog_humio_logs	ingress throughput	+0.81	[+0.73, +0.89]	100.00%
datadog_agent_remap_datadog_logs_acks	ingress throughput	+0.61	[+0.52, +0.71]	100.00%
http_to_http_json	ingress throughput	+0.51	[+0.45, +0.57]	100.00%
otlp_grpc_to_blackhole	ingress throughput	+0.48	[+0.36, +0.59]	100.00%
enterprise_http_to_http	ingress throughput	+0.04	[+0.01, +0.08]	89.63%
http_to_http_noack	ingress throughput	+0.04	[-0.01, +0.10]	67.09%
splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.04	[-0.03, +0.11]	55.10%
fluent_elasticsearch	ingress throughput	-0.00	[-0.00, +0.00]	55.71%
splunk_hec_indexer_ack_blackhole	ingress throughput	-0.01	[-0.05, +0.04]	16.44%
splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.02	[-0.06, +0.03]	40.53%
splunk_hec_route_s3	ingress throughput	-0.15	[-0.30, -0.00]	80.11%
socket_to_socket_blackhole	ingress throughput	-0.40	[-0.45, -0.34]	100.00%
syslog_splunk_hec_logs	ingress throughput	-0.46	[-0.53, -0.39]	100.00%
syslog_log2metric_humio_metrics	ingress throughput	-1.32	[-1.40, -1.25]	100.00%
syslog_log2metric_splunk_hec_metrics	ingress throughput	-1.47	[-1.55, -1.39]	100.00%
http_to_http_acks	ingress throughput	-1.60	[-2.81, -0.38]	90.82%
datadog_agent_remap_blackhole_acks	ingress throughput	-1.67	[-1.75, -1.59]	100.00%
file_to_blackhole	egress throughput	-2.87	[-6.68, +0.93]	66.65%
syslog_loki	ingress throughput	-4.96	[-5.08, -4.84]	100.00%

[github-actions]

Regression Detector Results

Run ID: 1b607f27-9510-4021-9b86-8c27d8d809ed
Baseline: 7a55210
Comparison: 657758d
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
file_to_blackhole	egress throughput	+2.74	[-1.19, +6.67]	62.82%
syslog_log2metric_splunk_hec_metrics	ingress throughput	+1.77	[+1.70, +1.85]	100.00%
http_to_http_json	ingress throughput	+1.53	[+1.46, +1.60]	100.00%
http_to_http_acks	ingress throughput	+1.35	[+0.11, +2.59]	83.66%
syslog_loki	ingress throughput	+1.01	[+0.93, +1.08]	100.00%
datadog_agent_remap_datadog_logs	ingress throughput	+1.00	[+0.90, +1.09]	100.00%
syslog_log2metric_humio_metrics	ingress throughput	+0.83	[+0.77, +0.90]	100.00%
syslog_humio_logs	ingress throughput	+0.63	[+0.56, +0.70]	100.00%
otlp_grpc_to_blackhole	ingress throughput	+0.62	[+0.51, +0.73]	100.00%
otlp_http_to_blackhole	ingress throughput	+0.62	[+0.43, +0.80]	100.00%
datadog_agent_remap_datadog_logs_acks	ingress throughput	+0.42	[+0.32, +0.52]	100.00%
enterprise_http_to_http	ingress throughput	+0.03	[-0.00, +0.06]	74.57%
http_to_http_noack	ingress throughput	+0.02	[-0.05, +0.08]	24.40%
splunk_hec_indexer_ack_blackhole	ingress throughput	+0.01	[-0.04, +0.05]	15.50%
splunk_hec_to_splunk_hec_logs_acks	ingress throughput	-0.00	[-0.06, +0.06]	0.07%
fluent_elasticsearch	ingress throughput	-0.00	[-0.00, +0.00]	5.45%
splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.03	[-0.07, +0.02]	56.52%
syslog_regex_logs2metric_ddmetrics	ingress throughput	-0.03	[-0.25, +0.19]	14.69%
syslog_splunk_hec_logs	ingress throughput	-0.08	[-0.16, -0.01]	85.27%
splunk_hec_route_s3	ingress throughput	-0.32	[-0.45, -0.19]	99.79%
socket_to_socket_blackhole	ingress throughput	-0.55	[-0.60, -0.50]	100.00%
datadog_agent_remap_blackhole	ingress throughput	-0.80	[-0.90, -0.70]	100.00%
http_text_to_http_json	ingress throughput	-1.50	[-1.56, -1.44]	100.00%
datadog_agent_remap_blackhole_acks	ingress throughput	-1.63	[-1.74, -1.52]	100.00%