vectordotdev / vector

A high-performance observability data pipeline.
https://vector.dev
Mozilla Public License 2.0
17.56k stars 1.54k forks source link

chore(deps): Bump libc from 0.2.158 to 0.2.159 #21351

Closed dependabot[bot] closed 37 minutes ago

dependabot[bot] commented 2 days ago

Bumps libc from 0.2.158 to 0.2.159.

Release notes

Sourced from libc's releases.

0.2.159

Added

Fixed

Changed

Changelog

Sourced from libc's changelog.

0.2.159 - 2024-09-24

Added

Fixed

Changed

Commits
  • 7373a1a chore: release (#3862)
  • 48668be Merge pull request #3931 from tgross35/backport-remove-tmp-file
  • 28bb64b Remove temporary file that was added by accident
  • a515d07 Merge pull request #3904 from tgross35/backport-buildrs-fix
  • abcb8f8 Simplify the RUSTC_WRAPPER check
  • 5078335 Fix rustc version when clippy-driver is used
  • 57a7d46 Merge pull request #3902 from tgross35/backport-horizon-network
  • a3e8869 Revise network definitions for HorizonOS
  • fdd3a26 Merge pull request #3900 from tgross35/espid-cherry-pick
  • 35060e8 Merge pull request #3901 from tgross35/backport-epoll_pwait2
  • Additional commits viewable in compare view


Dependabot compatibility score

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 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[bot] commented 53 minutes ago

Regression Detector Results

Run ID: 67e78642-1ddd-4d1a-978b-81b7de98d1fd Metrics dashboard

Baseline: 77ce3e59c69663223b0185e922c91af389759889 Comparison: 74134299dd78055921d9705035a6c7b582db462d

Performance changes are noted in the perf column of each table:

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.53 | [-11.12, +2.05] | |

Fine details of change detection per experiment

| perf | experiment | goal | Δ mean % | Δ mean % CI | links | |------|---------------------------------------------------|--------------------|----------|-----------------|-------| | ➖ | fluent_elasticsearch | ingress throughput | +3.65 | [+3.14, +4.15] | | | ➖ | http_text_to_http_json | ingress throughput | +3.28 | [+3.12, +3.45] | | | ➖ | splunk_hec_route_s3 | ingress throughput | +2.75 | [+2.41, +3.08] | | | ➖ | syslog_log2metric_humio_metrics | ingress throughput | +1.94 | [+1.79, +2.08] | | | ➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | +1.41 | [+1.26, +1.55] | | | ➖ | datadog_agent_remap_blackhole | ingress throughput | +1.35 | [+1.24, +1.47] | | | ➖ | http_elasticsearch | ingress throughput | +1.29 | [+1.10, +1.48] | | | ➖ | datadog_agent_remap_blackhole_acks | ingress throughput | +0.96 | [+0.83, +1.08] | | | ➖ | http_to_http_noack | ingress throughput | +0.20 | [+0.10, +0.29] | | | ➖ | http_to_http_json | ingress throughput | +0.06 | [+0.01, +0.11] | | | ➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | +0.01 | [-0.07, +0.10] | | | ➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | +0.00 | [-0.09, +0.09] | | | ➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | +0.00 | [-0.10, +0.10] | | | ➖ | datadog_agent_remap_datadog_logs | ingress throughput | -0.03 | [-0.25, +0.18] | | | ➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | -0.17 | [-0.30, -0.04] | | | ➖ | http_to_http_acks | ingress throughput | -0.18 | [-1.40, +1.04] | | | ➖ | otlp_grpc_to_blackhole | ingress throughput | -0.20 | [-0.31, -0.09] | | | ➖ | http_to_s3 | ingress throughput | -0.65 | [-0.94, -0.37] | | | ➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | -1.07 | [-1.30, -0.83] | | | ➖ | syslog_splunk_hec_logs | ingress throughput | -1.39 | [-1.50, -1.29] | | | ➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | -1.87 | [-1.94, -1.80] | | | ➖ | syslog_loki | ingress throughput | -1.93 | [-2.03, -1.82] | | | ➖ | socket_to_socket_blackhole | ingress throughput | -2.92 | [-2.99, -2.85] | | | ➖ | otlp_http_to_blackhole | ingress throughput | -2.98 | [-3.09, -2.87] | | | ➖ | syslog_humio_logs | ingress throughput | -3.31 | [-3.40, -3.22] | | | ➖ | file_to_blackhole | egress throughput | -4.53 | [-11.12, +2.05] | |

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