trafficstars

Bumps bollard from 0.16.1 to 0.17.0.

Release notes

Release v0.17.0

What's Changed

Add repository field to codegen crates by @paolobarbolini in fussybeaver/bollard#398

protobuf fetch script by @fussybeaver in fussybeaver/bollard#402

Upgrade to rustls 0.23 by @fussybeaver in fussybeaver/bollard#403

feat: Add secrets implementation to buildkit by @fussybeaver in fussybeaver/bollard#404

fix doc by @cn-kali-team in fussybeaver/bollard#406

Fixes for UpdateContainerOptions by @paul-hansen in fussybeaver/bollard#410

build(deps): update base64 requirement from 0.21 to 0.22 by @dependabot in fussybeaver/bollard#405

build(deps): update termion requirement from 3.0 to 4.0 by @dependabot in fussybeaver/bollard#407

#380: Add streaming image import by @russelltg in fussybeaver/bollard#411

chore: Update dependencies by @reneleonhardt in fussybeaver/bollard#413

fix: improve socket error handling by @KMJ-007 in fussybeaver/bollard#414

Enable sshforwarding to local ssh agent in buildkit by @fussybeaver in fussybeaver/bollard#416

build: Bump CircleCI docker image to 27.0 by @fussybeaver in fussybeaver/bollard#429

fix: Don't populate X-Registry-* headers when credentials are not set by @eplightning in fussybeaver/bollard#430

Bump protobuf dependencies by @fussybeaver in fussybeaver/bollard#431

fix: Fetch GRPC anonymous token correctly by @fussybeaver in fussybeaver/bollard#432

build(deps): update base64 requirement from 0.21 to 0.22 in /codegen/swagger by @dependabot in fussybeaver/bollard#435

build(deps): update bollard-stubs requirement from =1.44.0-rc.2 to =1.45.0-rc.26.0.1 by @dependabot in fussybeaver/bollard#434

Peg to API 1.45 moby release v26.0.1 by @fussybeaver in fussybeaver/bollard#437

Release 0.17.0 by @fussybeaver in fussybeaver/bollard#439

New Contributors

@paolobarbolini made their first contribution in fussybeaver/bollard#398

@cn-kali-team made their first contribution in fussybeaver/bollard#406

@paul-hansen made their first contribution in fussybeaver/bollard#410

@russelltg made their first contribution in fussybeaver/bollard#411

@reneleonhardt made their first contribution in fussybeaver/bollard#413

@KMJ-007 made their first contribution in fussybeaver/bollard#414

@eplightning made their first contribution in fussybeaver/bollard#430

Full Changelog: https://github.com/fussybeaver/bollard/compare/v0.16.1...v0.17.0

Commits

01413b7 Merge pull request #439 from fussybeaver/ND/release-0.17.0
04893e4 chore: Release 0.17.0
0802fe8 build: Remove --locked from cargo-audit
8c48d86 chore: Clippy fixes for Rust 1.80
7ecb05c build: Bump Rust to version 1.80
5d5e8e0 docs: Update README for 0.17.0
865805f Merge pull request #437 from fussybeaver/ND/stubs-26.0.1
2f9f280 chore: Peg at API version 1.45
6e9a516 chore: Use hyperlocal 0.9.0
f99b2a5 build: Generate bollard-models v26.0.1 API v1.45
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)

Jul 29 '24 04:07 dependabot[bot]

Datadog Report

Branch report: dependabot/cargo/bollard-0.17.0 Commit report: fe222ba Test service: vector

:white_check_mark: 0 Failed, 7 Passed, 0 Skipped, 25.47s Total Time

Jul 30 '24 21:07 datadog-vectordotdev[bot]

Regression Detector Results

Run ID: 58b8677c-c5e4-46e8-9142-4e239a468a4d Metrics dashboard

Baseline: d982b82e0c04a4c3e46eab02faa4942e30c8e600 Comparison: 939e7ab5c9c2d6c004ca65879bedaac03ef15c8d

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.

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI	links
➖	file_to_blackhole	egress throughput	+4.12	[-2.73, +10.97]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	file_to_blackhole	egress throughput	+4.12	[-2.73, +10.97]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	+3.50	[+3.36, +3.63]
➖	otlp_http_to_blackhole	ingress throughput	+2.09	[+1.96, +2.22]
➖	syslog_humio_logs	ingress throughput	+1.54	[+1.41, +1.67]
➖	http_to_http_acks	ingress throughput	+1.53	[+0.19, +2.87]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	+1.49	[+1.37, +1.60]
➖	splunk_hec_route_s3	ingress throughput	+0.54	[+0.22, +0.85]
➖	http_text_to_http_json	ingress throughput	+0.20	[+0.06, +0.33]
➖	http_to_s3	ingress throughput	+0.18	[-0.09, +0.46]
➖	http_to_http_noack	ingress throughput	+0.09	[+0.03, +0.15]
➖	http_to_http_json	ingress throughput	+0.06	[+0.01, +0.11]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	+0.03	[-0.08, +0.13]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	-0.00	[-0.09, +0.09]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	-0.01	[-0.11, +0.09]
➖	datadog_agent_remap_blackhole	ingress throughput	-0.10	[-0.19, -0.01]
➖	http_elasticsearch	ingress throughput	-0.34	[-0.53, -0.15]
➖	syslog_loki	ingress throughput	-0.48	[-0.56, -0.39]
➖	fluent_elasticsearch	ingress throughput	-0.63	[-1.12, -0.15]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.73	[-0.91, -0.55]
➖	otlp_grpc_to_blackhole	ingress throughput	-0.91	[-1.02, -0.79]
➖	syslog_log2metric_humio_metrics	ingress throughput	-0.95	[-1.07, -0.82]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	-0.99	[-1.11, -0.87]
➖	datadog_agent_remap_datadog_logs	ingress throughput	-1.11	[-1.29, -0.93]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-1.25	[-1.34, -1.16]
➖	socket_to_socket_blackhole	ingress throughput	-1.93	[-1.97, -1.89]
➖	syslog_splunk_hec_logs	ingress throughput	-2.23	[-2.34, -2.13]

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:

Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
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.
Its configuration does not mark it "erratic".

Jul 31 '24 04:07 github-actions[bot]

Regression Detector Results

Run ID: cda67e82-a908-4e52-a573-387805e8c955 Metrics dashboard

Baseline: f56a1e086121a445e56a2514e971fa7f8a176639 Comparison: 202fe723c71d25e1f7be64b8be5f734e04d9886f

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.

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI	links
➖	file_to_blackhole	egress throughput	-4.16	[-10.96, +2.64]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	splunk_hec_route_s3	ingress throughput	+1.97	[+1.65, +2.29]
➖	fluent_elasticsearch	ingress throughput	+1.82	[+1.33, +2.31]
➖	http_to_http_acks	ingress throughput	+1.40	[+0.07, +2.73]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	+1.22	[+1.10, +1.34]
➖	otlp_grpc_to_blackhole	ingress throughput	+0.98	[+0.86, +1.10]
➖	http_to_s3	ingress throughput	+0.75	[+0.47, +1.03]
➖	datadog_agent_remap_datadog_logs	ingress throughput	+0.19	[-0.02, +0.40]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	+0.06	[-0.03, +0.16]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	+0.03	[-0.08, +0.14]
➖	http_to_http_json	ingress throughput	+0.03	[-0.01, +0.06]
➖	http_to_http_noack	ingress throughput	+0.02	[-0.02, +0.05]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.00	[-0.12, +0.12]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	-0.01	[-0.09, +0.07]
➖	datadog_agent_remap_blackhole	ingress throughput	-0.23	[-0.35, -0.11]
➖	http_elasticsearch	ingress throughput	-0.35	[-0.55, -0.16]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	-1.08	[-1.24, -0.91]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	-1.31	[-1.48, -1.15]
➖	syslog_loki	ingress throughput	-1.72	[-1.77, -1.67]
➖	http_text_to_http_json	ingress throughput	-1.96	[-2.07, -1.84]
➖	otlp_http_to_blackhole	ingress throughput	-2.54	[-2.70, -2.38]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-2.61	[-2.73, -2.49]
➖	syslog_log2metric_humio_metrics	ingress throughput	-2.67	[-2.80, -2.54]
➖	syslog_splunk_hec_logs	ingress throughput	-3.05	[-3.15, -2.95]
➖	socket_to_socket_blackhole	ingress throughput	-3.78	[-3.84, -3.71]
➖	syslog_humio_logs	ingress throughput	-3.89	[-4.01, -3.77]
➖	file_to_blackhole	egress throughput	-4.16	[-10.96, +2.64]

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:

Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
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.
Its configuration does not mark it "erratic".

Jul 31 '24 05:07 github-actions[bot]

Regression Detector Results

Run ID: c91ba612-c779-4965-869a-00ac02921f69 Metrics dashboard

Baseline: 06a0dfa44c36f91b290bace14271b3175ff0cf09 Comparison: 7d61cd9c6eea4e76c8dc0093e080dbd84e49ad1c

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	links
❌	syslog_regex_logs2metric_ddmetrics	ingress throughput	-6.45	[-6.63, -6.27]

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI	links
➖	file_to_blackhole	egress throughput	+3.49	[-3.62, +10.59]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	syslog_humio_logs	ingress throughput	+3.82	[+3.69, +3.95]
➖	file_to_blackhole	egress throughput	+3.49	[-3.62, +10.59]
➖	fluent_elasticsearch	ingress throughput	+1.58	[+1.09, +2.07]
➖	http_text_to_http_json	ingress throughput	+1.54	[+1.40, +1.69]
➖	socket_to_socket_blackhole	ingress throughput	+1.39	[+1.35, +1.43]
➖	datadog_agent_remap_blackhole	ingress throughput	+1.13	[+1.04, +1.22]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	+0.57	[+0.45, +0.69]
➖	splunk_hec_route_s3	ingress throughput	+0.45	[+0.12, +0.78]
➖	http_elasticsearch	ingress throughput	+0.37	[+0.21, +0.52]
➖	http_to_http_json	ingress throughput	+0.05	[+0.00, +0.10]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.02	[-0.11, +0.14]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	+0.01	[-0.09, +0.11]
➖	http_to_http_noack	ingress throughput	-0.00	[-0.02, +0.02]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	-0.02	[-0.11, +0.06]
➖	http_to_http_acks	ingress throughput	-0.03	[-1.36, +1.29]
➖	http_to_s3	ingress throughput	-0.15	[-0.42, +0.12]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.27	[-0.44, -0.10]
➖	datadog_agent_remap_datadog_logs	ingress throughput	-0.31	[-0.50, -0.13]
➖	syslog_loki	ingress throughput	-0.97	[-1.04, -0.89]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-1.40	[-1.52, -1.28]
➖	syslog_splunk_hec_logs	ingress throughput	-1.48	[-1.64, -1.32]
➖	otlp_grpc_to_blackhole	ingress throughput	-1.54	[-1.66, -1.43]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-1.88	[-2.02, -1.73]
➖	syslog_log2metric_humio_metrics	ingress throughput	-2.64	[-2.77, -2.51]
➖	otlp_http_to_blackhole	ingress throughput	-3.94	[-4.10, -3.78]
❌	syslog_regex_logs2metric_ddmetrics	ingress throughput	-6.45	[-6.63, -6.27]

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:

Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
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.
Its configuration does not mark it "erratic".

Aug 09 '24 17:08 github-actions[bot]

Regression Detector Results

Run ID: 5bee75f6-a7ad-420f-8813-90bb3f880942 Metrics dashboard

Baseline: 16d2300bd8def42248e49e42643c8c1a604835c8 Comparison: b7cf0befe4a7bc917a8d6e25bc629385bcae72cb

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	links
❌	syslog_regex_logs2metric_ddmetrics	ingress throughput	-5.67	[-5.77, -5.57]

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI	links
✅	file_to_blackhole	egress throughput	+7.83	[+0.40, +15.26]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
✅	file_to_blackhole	egress throughput	+7.83	[+0.40, +15.26]
➖	syslog_humio_logs	ingress throughput	+3.52	[+3.30, +3.73]
➖	http_elasticsearch	ingress throughput	+3.12	[+2.93, +3.31]
➖	fluent_elasticsearch	ingress throughput	+2.97	[+2.46, +3.48]
➖	datadog_agent_remap_blackhole	ingress throughput	+1.16	[+1.01, +1.31]
➖	syslog_splunk_hec_logs	ingress throughput	+0.99	[+0.91, +1.08]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	+0.87	[+0.64, +1.10]
➖	datadog_agent_remap_datadog_logs	ingress throughput	+0.68	[+0.45, +0.91]
➖	http_to_http_acks	ingress throughput	+0.44	[-0.89, +1.76]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	+0.30	[+0.18, +0.41]
➖	socket_to_socket_blackhole	ingress throughput	+0.25	[+0.17, +0.32]
➖	http_text_to_http_json	ingress throughput	+0.08	[-0.07, +0.23]
➖	http_to_http_json	ingress throughput	+0.03	[-0.00, +0.07]
➖	http_to_http_noack	ingress throughput	+0.03	[-0.01, +0.07]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	+0.03	[-0.07, +0.12]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	+0.00	[-0.08, +0.09]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.00	[-0.12, +0.12]
➖	http_to_s3	ingress throughput	-0.53	[-0.81, -0.26]
➖	syslog_loki	ingress throughput	-0.67	[-0.74, -0.60]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-0.81	[-0.93, -0.68]
➖	splunk_hec_route_s3	ingress throughput	-0.83	[-1.16, -0.49]
➖	otlp_grpc_to_blackhole	ingress throughput	-1.14	[-1.26, -1.03]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	-1.70	[-1.84, -1.56]
➖	syslog_log2metric_humio_metrics	ingress throughput	-2.32	[-2.48, -2.16]
➖	otlp_http_to_blackhole	ingress throughput	-3.05	[-3.21, -2.90]
❌	syslog_regex_logs2metric_ddmetrics	ingress throughput	-5.67	[-5.77, -5.57]

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:

Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
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.
Its configuration does not mark it "erratic".

Aug 09 '24 18:08 github-actions[bot]

@dependabot rebase

Aug 12 '24 18:08 jszwedko

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

Aug 12 '24 18:08 dependabot[bot]

@dependabot recreate

Aug 12 '24 18:08 jszwedko

Regression Detector Results

Run ID: d90e2d54-9f8f-4a31-9f9b-536859964649 Metrics dashboard

Baseline: f371bc2ce5a806a4dc9fa8ba573594dabb2a60ea Comparison: 661d530defb1e6923eb9e8b3c65e2988941e2efc

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.

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI	links
➖	file_to_blackhole	egress throughput	+2.47	[-4.53, +9.47]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	+4.79	[+4.62, +4.96]
➖	syslog_humio_logs	ingress throughput	+3.68	[+3.56, +3.80]
➖	socket_to_socket_blackhole	ingress throughput	+2.79	[+2.72, +2.85]
➖	file_to_blackhole	egress throughput	+2.47	[-4.53, +9.47]
➖	otlp_http_to_blackhole	ingress throughput	+2.36	[+2.21, +2.52]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	+2.26	[+2.15, +2.37]
➖	datadog_agent_remap_datadog_logs	ingress throughput	+1.24	[+1.04, +1.44]
➖	syslog_loki	ingress throughput	+0.93	[+0.85, +1.01]
➖	datadog_agent_remap_blackhole	ingress throughput	+0.91	[+0.82, +1.00]
➖	syslog_splunk_hec_logs	ingress throughput	+0.88	[+0.80, +0.95]
➖	http_to_http_acks	ingress throughput	+0.67	[-0.65, +1.99]
➖	otlp_grpc_to_blackhole	ingress throughput	+0.63	[+0.49, +0.76]
➖	http_to_http_json	ingress throughput	+0.08	[+0.02, +0.14]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.00	[-0.11, +0.11]
➖	http_to_http_noack	ingress throughput	+0.00	[-0.02, +0.02]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	+0.00	[-0.10, +0.10]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	-0.01	[-0.10, +0.07]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.24	[-0.43, -0.06]
➖	http_to_s3	ingress throughput	-0.33	[-0.60, -0.07]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-0.47	[-0.56, -0.38]
➖	splunk_hec_route_s3	ingress throughput	-0.58	[-0.90, -0.25]
➖	http_elasticsearch	ingress throughput	-0.84	[-0.99, -0.68]
➖	fluent_elasticsearch	ingress throughput	-1.38	[-1.88, -0.88]
➖	http_text_to_http_json	ingress throughput	-1.61	[-1.73, -1.50]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-3.19	[-3.31, -3.07]
➖	syslog_log2metric_humio_metrics	ingress throughput	-4.03	[-4.17, -3.90]

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:

Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
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.
Its configuration does not mark it "erratic".

Aug 17 '24 04:08 github-actions[bot]

A newer version of bollard 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.

Aug 19 '24 04:08 dependabot[bot]

Regression Detector Results

Run ID: 57ce4826-7c87-41ae-bea1-41fbbc1c62be Metrics dashboard

Baseline: 76a525b17368a3b656ff7d3c76ef8feb28fd4908 Comparison: eabf624d40556d0f4e3af7f6de5f90a4ab2cfe47

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.

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI	links
❌	file_to_blackhole	egress throughput	-20.29	[-26.37, -14.22]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	+3.06	[+2.89, +3.23]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	+2.05	[+1.88, +2.23]
➖	syslog_log2metric_humio_metrics	ingress throughput	+1.92	[+1.78, +2.06]
➖	http_text_to_http_json	ingress throughput	+1.60	[+1.47, +1.74]
➖	http_to_http_acks	ingress throughput	+1.29	[-0.03, +2.61]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	+1.25	[+1.15, +1.34]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	+0.46	[+0.33, +0.59]
➖	syslog_loki	ingress throughput	+0.34	[+0.26, +0.42]
➖	http_elasticsearch	ingress throughput	+0.31	[+0.14, +0.48]
➖	http_to_http_noack	ingress throughput	+0.22	[+0.12, +0.32]
➖	http_to_s3	ingress throughput	+0.07	[-0.20, +0.34]
➖	http_to_http_json	ingress throughput	+0.03	[-0.01, +0.06]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	+0.02	[-0.08, +0.12]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.00	[-0.10, +0.11]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	+0.00	[-0.08, +0.08]
➖	syslog_humio_logs	ingress throughput	-0.04	[-0.21, +0.14]
➖	fluent_elasticsearch	ingress throughput	-0.04	[-0.53, +0.45]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-0.07	[-0.21, +0.07]
➖	datadog_agent_remap_blackhole	ingress throughput	-0.16	[-0.28, -0.04]
➖	datadog_agent_remap_datadog_logs	ingress throughput	-0.31	[-0.52, -0.10]
➖	otlp_http_to_blackhole	ingress throughput	-0.86	[-0.98, -0.74]
➖	otlp_grpc_to_blackhole	ingress throughput	-1.04	[-1.15, -0.93]
➖	socket_to_socket_blackhole	ingress throughput	-1.14	[-1.22, -1.06]
➖	syslog_splunk_hec_logs	ingress throughput	-1.73	[-1.86, -1.60]
➖	splunk_hec_route_s3	ingress throughput	-2.88	[-3.21, -2.55]
❌	file_to_blackhole	egress throughput	-20.29	[-26.37, -14.22]

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:

Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
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.
Its configuration does not mark it "erratic".

Aug 21 '24 00:08 github-actions[bot]

Regression Detector Results

Run ID: 9633b817-d59d-4f02-beee-a194b4f7ee00 Metrics dashboard

Baseline: 0fd80ef11dba206c2a190e2364a299aaceb4359a Comparison: 84d76b8983e38f47d254c517e5cefabb1cd97d80

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.

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI	links
✅	file_to_blackhole	egress throughput	+28.25	[+20.24, +36.26]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
✅	file_to_blackhole	egress throughput	+28.25	[+20.24, +36.26]
➖	syslog_log2metric_humio_metrics	ingress throughput	+3.05	[+2.90, +3.20]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	+2.63	[+2.52, +2.74]
➖	socket_to_socket_blackhole	ingress throughput	+2.57	[+2.50, +2.65]
➖	syslog_splunk_hec_logs	ingress throughput	+1.80	[+1.69, +1.91]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	+1.65	[+1.54, +1.76]
➖	datadog_agent_remap_datadog_logs	ingress throughput	+0.59	[+0.42, +0.76]
➖	otlp_http_to_blackhole	ingress throughput	+0.55	[+0.40, +0.70]
➖	fluent_elasticsearch	ingress throughput	+0.51	[+0.01, +1.01]
➖	syslog_loki	ingress throughput	+0.51	[+0.41, +0.61]
➖	http_to_http_noack	ingress throughput	+0.19	[+0.10, +0.27]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	+0.17	[+0.08, +0.27]
➖	http_to_http_json	ingress throughput	+0.10	[+0.04, +0.17]
➖	http_to_s3	ingress throughput	+0.07	[-0.19, +0.34]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	+0.02	[-0.08, +0.12]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	-0.00	[-0.08, +0.08]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	-0.01	[-0.12, +0.11]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-0.01	[-0.13, +0.11]
➖	http_elasticsearch	ingress throughput	-0.01	[-0.19, +0.16]
➖	splunk_hec_route_s3	ingress throughput	-0.09	[-0.40, +0.21]
➖	http_to_http_acks	ingress throughput	-0.12	[-1.43, +1.20]
➖	syslog_humio_logs	ingress throughput	-0.19	[-0.27, -0.10]
➖	otlp_grpc_to_blackhole	ingress throughput	-0.31	[-0.42, -0.19]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.33	[-0.58, -0.07]
➖	datadog_agent_remap_blackhole	ingress throughput	-0.34	[-0.44, -0.23]
➖	http_text_to_http_json	ingress throughput	-2.07	[-2.19, -1.94]

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:

Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
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.
Its configuration does not mark it "erratic".

Aug 22 '24 00:08 github-actions[bot]

Regression Detector Results

Run ID: abff266d-4e9e-4577-9c65-b6da09949538 Metrics dashboard

Baseline: 143e01714c2e1011fa00f12b014ecd37c3dd4050 Comparison: 2807859c259df90878b689d3fdec7ed31f8c38f8

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.

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI	links
❌	file_to_blackhole	egress throughput	-12.68	[-19.11, -6.26]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	http_elasticsearch	ingress throughput	+2.96	[+2.78, +3.14]
➖	fluent_elasticsearch	ingress throughput	+2.37	[+1.87, +2.86]
➖	datadog_agent_remap_blackhole	ingress throughput	+1.41	[+1.30, +1.52]
➖	otlp_http_to_blackhole	ingress throughput	+1.06	[+0.92, +1.20]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	+0.19	[+0.07, +0.31]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	+0.15	[+0.03, +0.27]
➖	http_to_http_noack	ingress throughput	+0.14	[+0.06, +0.21]
➖	http_to_http_acks	ingress throughput	+0.12	[-1.20, +1.43]
➖	http_to_http_json	ingress throughput	+0.08	[+0.02, +0.13]
➖	http_to_s3	ingress throughput	+0.05	[-0.22, +0.32]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	+0.02	[-0.06, +0.10]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	+0.01	[-0.09, +0.10]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.00	[-0.10, +0.11]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-0.26	[-0.36, -0.17]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	-0.29	[-0.40, -0.18]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.34	[-0.55, -0.12]
➖	http_text_to_http_json	ingress throughput	-0.51	[-0.62, -0.40]
➖	otlp_grpc_to_blackhole	ingress throughput	-0.92	[-1.03, -0.80]
➖	syslog_humio_logs	ingress throughput	-0.94	[-1.07, -0.81]
➖	syslog_loki	ingress throughput	-1.73	[-1.81, -1.65]
➖	syslog_log2metric_humio_metrics	ingress throughput	-2.30	[-2.45, -2.15]
➖	splunk_hec_route_s3	ingress throughput	-2.36	[-2.67, -2.04]
➖	datadog_agent_remap_datadog_logs	ingress throughput	-2.39	[-2.57, -2.20]
➖	syslog_splunk_hec_logs	ingress throughput	-2.72	[-2.82, -2.61]
➖	socket_to_socket_blackhole	ingress throughput	-3.79	[-3.86, -3.72]
❌	file_to_blackhole	egress throughput	-12.68	[-19.11, -6.26]

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:

Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
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.
Its configuration does not mark it "erratic".

Aug 22 '24 01:08 github-actions[bot]

@dependabot recreate

Jun 23 '25 14:06 thomasqueirozb

Datadog Report

Branch report: dependabot/cargo/bollard-0.17.0 Commit report: 52ca691 Test service: vector

:white_check_mark: 0 Failed, 7 Passed, 0 Skipped, 25.25s Total Time

Jun 23 '25 18:06 datadog-vectordotdev[bot]

vector vector copied to clipboard

chore(deps): Bump bollard from 0.16.1 to 0.17.0

Release v0.17.0

What's Changed

New Contributors

Datadog Report

Regression Detector Results

No significant changes in experiment optimization goals

Experiments ignored for regressions

Fine details of change detection per experiment

Explanation

Regression Detector Results

No significant changes in experiment optimization goals

Experiments ignored for regressions

Fine details of change detection per experiment

Explanation

Regression Detector Results

Significant changes in experiment optimization goals

Experiments ignored for regressions

Fine details of change detection per experiment

Explanation

Regression Detector Results

Significant changes in experiment optimization goals

Experiments ignored for regressions

Fine details of change detection per experiment

Explanation

Regression Detector Results

No significant changes in experiment optimization goals

Experiments ignored for regressions

Fine details of change detection per experiment

Explanation

Regression Detector Results

No significant changes in experiment optimization goals

Experiments ignored for regressions

Fine details of change detection per experiment

Explanation

Regression Detector Results

No significant changes in experiment optimization goals

Experiments ignored for regressions

Fine details of change detection per experiment

Explanation

Regression Detector Results

No significant changes in experiment optimization goals

Experiments ignored for regressions

Fine details of change detection per experiment

Explanation

Datadog Report

vector
vector copied to clipboard