search

DataDog / saluki

An experimental toolkit for building telemetry data planes in Rust.
Apache License 2.0
12 stars 2 forks source link

build(deps): bump async-trait from 0.1.81 to 0.1.82 #229

Closed dependabot[bot] closed 1 week ago

dependabot[bot] commented 1 week ago

Bumps async-trait from 0.1.81 to 0.1.82.

Release notes

Sourced from async-trait's releases.

0.1.82

  • Prevent elided_named_lifetimes lint being produced in generated code (#276)
Commits
  • f8e5bb4 Release 0.1.82
  • 8fbf118 Merge pull request #276 from dtolnay/elidednamed
  • 6fa246a Ignore nightly's new elided_named_lifetimes lint in generated code
  • d542a0d Upload CI Cargo.lock for reproducing failures
  • 8828c35 Sort dependency features in Cargo.toml
  • ba9793a Update ui test suite to nightly-2024-08-11
  • 82c62cd Update ui test suite to nightly-2024-07-25
  • 370ee12 Update ui test suite to nightly-2024-07-20
  • See full diff 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)
pr-commenter[bot] commented 1 week ago

Regression Detector (DogStatsD)

Regression Detector Results

Run ID: 590df30f-dada-4f7a-ad37-a5391edc2911

Baseline: 7.55.2 Comparison: 7.55.3

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.

Fine details of change detection per experiment

| perf | experiment | goal | Δ mean % | Δ mean % CI | links | |------|----------------------------------------------|--------------------|----------|----------------|-------| | ➖ | dsd_uds_512kb_3k_contexts | ingress throughput | +0.03 | [-0.02, +0.08] | | | ➖ | dsd_uds_100mb_3k_contexts_distributions_only | memory utilization | +0.03 | [-0.18, +0.24] | | | ➖ | dsd_uds_100mb_250k_contexts | ingress throughput | +0.00 | [-0.01, +0.01] | | | ➖ | dsd_uds_1mb_3k_contexts | ingress throughput | -0.00 | [-0.08, +0.08] | | | ➖ | dsd_uds_100mb_3k_contexts | ingress throughput | -0.00 | [-0.02, +0.01] | | | ➖ | dsd_uds_500mb_3k_contexts | ingress throughput | -0.00 | [-0.01, +0.00] | | | ➖ | dsd_uds_1mb_50k_contexts | ingress throughput | -0.02 | [-0.03, -0.00] | | | ➖ | dsd_uds_1mb_50k_contexts_memlimit | ingress throughput | -0.02 | [-0.04, +0.01] | | | ➖ | dsd_uds_10mb_3k_contexts | ingress throughput | -0.04 | [-0.08, -0.00] | |

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".
pr-commenter[bot] commented 1 week ago

Regression Detector (Saluki)

Regression Detector Results

Run ID: 613c8cb9-4b29-4eee-9890-55ace426fde6

Baseline: 95b2925da12ba98980e5b9b66df61aa89726bbe0 Comparison: f8c8528278a7af5019e91e5db3dbeedf05c7c5a3

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.

Fine details of change detection per experiment

| perf | experiment | goal | Δ mean % | Δ mean % CI | links | |------|-------------------------------------------------|--------------------|----------|----------------|-------| | ➖ | dsd_uds_500mb_3k_contexts | ingress throughput | +2.20 | [+2.11, +2.29] | | | ➖ | dsd_uds_100mb_3k_contexts_distributions_only | memory utilization | +2.18 | [+2.05, +2.31] | | | ➖ | dsd_uds_10mb_3k_contexts | ingress throughput | +0.02 | [-0.04, +0.09] | | | ➖ | dsd_uds_1mb_50k_contexts | ingress throughput | +0.02 | [-0.01, +0.04] | | | ➖ | dsd_uds_50mb_10k_contexts_no_inlining_no_allocs | ingress throughput | +0.01 | [-0.02, +0.04] | | | ➖ | dsd_uds_100mb_3k_contexts | ingress throughput | +0.01 | [-0.00, +0.02] | | | ➖ | dsd_uds_50mb_10k_contexts_no_inlining | ingress throughput | +0.00 | [-0.00, +0.00] | | | ➖ | dsd_uds_1mb_3k_contexts | ingress throughput | -0.01 | [-0.05, +0.03] | | | ➖ | dsd_uds_100mb_250k_contexts | ingress throughput | -0.03 | [-0.28, +0.23] | | | ➖ | dsd_uds_512kb_3k_contexts | ingress throughput | -0.06 | [-0.11, -0.00] | | | ➖ | dsd_uds_1mb_50k_contexts_memlimit | ingress throughput | -0.63 | [-3.84, +2.58] | |

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".
pr-commenter[bot] commented 1 week ago

Regression Detector Links

Experiment Result Links

experiment link(s)
dsd_uds_100mb_250k_contexts [Profiling (ADP)] [Profiling (DSD)] [SMP Dashboard]
dsd_uds_100mb_3k_contexts [Profiling (ADP)] [Profiling (DSD)] [SMP Dashboard]
dsd_uds_100mb_3k_contexts_distributions_only [Profiling (ADP)] [Profiling (DSD)] [SMP Dashboard]
dsd_uds_10mb_3k_contexts [Profiling (ADP)] [Profiling (DSD)] [SMP Dashboard]
dsd_uds_1mb_3k_contexts [Profiling (ADP)] [Profiling (DSD)] [SMP Dashboard]
dsd_uds_1mb_50k_contexts [Profiling (ADP)] [Profiling (DSD)] [SMP Dashboard]
dsd_uds_1mb_50k_contexts_memlimit [Profiling (ADP)] [Profiling (DSD)] [SMP Dashboard]
dsd_uds_500mb_3k_contexts [Profiling (ADP)] [Profiling (DSD)] [SMP Dashboard]
dsd_uds_512kb_3k_contexts [Profiling (ADP)] [Profiling (DSD)] [SMP Dashboard]
dsd_uds_50mb_10k_contexts_no_inlining (ADP only) [Profiling (ADP)] [SMP Dashboard]
dsd_uds_50mb_10k_contexts_no_inlining_no_allocs (ADP only) [Profiling (ADP)] [SMP Dashboard]
dependabot[bot] commented 1 week ago

Looks like async-trait is up-to-date now, so this is no longer needed.