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 tokio from 1.39.3 to 1.40.0 #228

Closed dependabot[bot] closed 1 week ago

dependabot[bot] commented 1 week ago

Bumps tokio from 1.39.3 to 1.40.0.

Release notes

Sourced from tokio's releases.

Tokio v1.40.0

1.40.0 (August 30th, 2024)

Added

  • io: add util::SimplexStream (#6589)
  • process: stabilize Command::process_group (#6731)
  • sync: add {TrySendError,SendTimeoutError}::into_inner (#6755)
  • task: add JoinSet::join_all (#6784)

Added (unstable)

  • runtime: add Builder::{on_task_spawn, on_task_terminate} (#6742)

Changed

  • io: use vectored io for write_all_buf when possible (#6724)
  • runtime: prevent niche-optimization to avoid triggering miri (#6744)
  • sync: mark mpsc types as UnwindSafe (#6783)
  • sync,time: make Sleep and BatchSemaphore instrumentation explicit roots (#6727)
  • task: use NonZeroU64 for task::Id (#6733)
  • task: include panic message when printing JoinError (#6753)
  • task: add #[must_use] to JoinHandle::abort_handle (#6762)
  • time: eliminate timer wheel allocations (#6779)

Documented

  • docs: clarify that [build] section doesn't go in Cargo.toml (#6728)
  • io: clarify zero remaining capacity case (#6790)
  • macros: improve documentation for select! (#6774)
  • sync: document mpsc channel allocation behavior (#6773)

#6589: tokio-rs/tokio#6589 #6724: tokio-rs/tokio#6724 #6727: tokio-rs/tokio#6727 #6728: tokio-rs/tokio#6728 #6731: tokio-rs/tokio#6731 #6733: tokio-rs/tokio#6733 #6742: tokio-rs/tokio#6742 #6744: tokio-rs/tokio#6744 #6753: tokio-rs/tokio#6753 #6755: tokio-rs/tokio#6755 #6762: tokio-rs/tokio#6762 #6773: tokio-rs/tokio#6773 #6774: tokio-rs/tokio#6774 #6779: tokio-rs/tokio#6779 #6783: tokio-rs/tokio#6783 #6784: tokio-rs/tokio#6784 #6790: tokio-rs/tokio#6790

Commits


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: dcda2d76-be04-479b-bae3-adfe4afa0591

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 | trials | links | |------|----------------------------------------------|--------------------|----------|----------------|--------|-------| | ➖ | dsd_uds_1mb_3k_contexts | ingress throughput | +0.04 | [-0.02, +0.09] | 1 | | | ➖ | dsd_uds_100mb_3k_contexts | ingress throughput | +0.01 | [-0.00, +0.02] | 1 | | | ➖ | dsd_uds_10mb_3k_contexts | ingress throughput | +0.01 | [-0.03, +0.05] | 1 | | | ➖ | dsd_uds_500mb_3k_contexts | ingress throughput | +0.00 | [-0.00, +0.01] | 1 | | | ➖ | dsd_uds_100mb_250k_contexts | ingress throughput | -0.00 | [-0.04, +0.04] | 1 | | | ➖ | dsd_uds_512kb_3k_contexts | ingress throughput | -0.02 | [-0.08, +0.05] | 1 | | | ➖ | dsd_uds_1mb_50k_contexts | ingress throughput | -0.03 | [-0.08, +0.01] | 1 | | | ➖ | dsd_uds_1mb_50k_contexts_memlimit | ingress throughput | -0.03 | [-0.06, -0.01] | 1 | | | ➖ | dsd_uds_100mb_3k_contexts_distributions_only | memory utilization | -0.79 | [-0.99, -0.58] | 1 | |

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: e974291a-063d-461f-abd4-8550f52bba55

Baseline: 159054ce70f4a012ff34e25659fd40f8d66fd5bd Comparison: d5e55b243c96e1c162b7bf868d3f069aeeaf2472

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 | trials | links | |------|-------------------------------------------------|--------------------|----------|----------------|--------|-------| | ➖ | dsd_uds_500mb_3k_contexts | ingress throughput | +0.56 | [+0.47, +0.64] | 1 | | | ➖ | dsd_uds_1mb_50k_contexts | ingress throughput | +0.05 | [+0.03, +0.07] | 1 | | | ➖ | dsd_uds_1mb_3k_contexts | ingress throughput | +0.02 | [-0.03, +0.07] | 1 | | | ➖ | dsd_uds_10mb_3k_contexts | ingress throughput | +0.02 | [-0.04, +0.07] | 1 | | | ➖ | dsd_uds_100mb_3k_contexts | ingress throughput | +0.00 | [-0.01, +0.01] | 1 | | | ➖ | dsd_uds_50mb_10k_contexts_no_inlining | ingress throughput | +0.00 | [-0.00, +0.00] | 1 | | | ➖ | dsd_uds_50mb_10k_contexts_no_inlining_no_allocs | ingress throughput | -0.01 | [-0.05, +0.04] | 1 | | | ➖ | dsd_uds_100mb_250k_contexts | ingress throughput | -0.02 | [-0.28, +0.24] | 1 | | | ➖ | dsd_uds_512kb_3k_contexts | ingress throughput | -0.03 | [-0.07, +0.01] | 1 | | | ➖ | dsd_uds_1mb_50k_contexts_memlimit | ingress throughput | -0.08 | [-3.36, +3.21] | 1 | | | ➖ | dsd_uds_100mb_3k_contexts_distributions_only | memory utilization | -1.85 | [-2.02, -1.67] | 1 | |

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 tokio is up-to-date now, so this is no longer needed.