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 serde_json from 1.0.124 to 1.0.125 #201

Closed dependabot[bot] closed 3 weeks ago

dependabot[bot] commented 3 weeks ago

Bumps serde_json from 1.0.124 to 1.0.125.

Release notes

Sourced from serde_json's releases.

1.0.125

  • Speed up \uXXXX parsing and improve handling of unpaired surrogates when deserializing to bytes (#1172, #1175, thanks @​purplesyringa)
Commits
  • 6130f9b Release 1.0.125
  • cc7a160 Touch up PR 1175
  • 0f942e5 Merge pull request 1175 from iex-rs/faster-backslash-u
  • d8921cd Merge pull request #1172 from iex-rs/faster-hex
  • b4bc643 Merge pull request #1176 from dtolnay/miriname
  • 94a2aad Improve job names for miri jobs
  • 8073fc1 Merge pull request #1174 from iex-rs/miri-on-ci
  • 96ae604 Correct WTF-8 parsing
  • 236cc82 Simplify unicode escape handling
  • 2f28d10 Use the same UTF-8/WTF-8 impl for surrogates
  • 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)
pr-commenter[bot] commented 3 weeks ago

Regression Detector (DogStatsD)

Regression Detector Results

Run ID: ed57f4b0-ed37-472f-9728-04ed07795fbc

Baseline: 7.52.0 Comparison: 7.52.1

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_100mb_3k_contexts_distributions_only | memory utilization | +0.54 | [+0.33, +0.75] | | | ➖ | dsd_uds_1mb_50k_contexts_memlimit | ingress throughput | +0.05 | [+0.00, +0.10] | | | ➖ | dsd_uds_100mb_3k_contexts | ingress throughput | +0.02 | [+0.01, +0.04] | | | ➖ | dsd_uds_100mb_250k_contexts | ingress throughput | +0.00 | [-0.03, +0.04] | | | ➖ | dsd_uds_500mb_3k_contexts | ingress throughput | +0.00 | [-0.00, +0.00] | | | ➖ | dsd_uds_10mb_3k_contexts | ingress throughput | -0.01 | [-0.04, +0.02] | | | ➖ | dsd_uds_1mb_3k_contexts | ingress throughput | -0.02 | [-0.09, +0.05] | | | ➖ | dsd_uds_1mb_50k_contexts | ingress throughput | -0.02 | [-0.05, +0.02] | | | ➖ | dsd_uds_512kb_3k_contexts | ingress throughput | -0.08 | [-0.14, -0.02] | |

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 3 weeks ago

Regression Detector (Saluki)

Regression Detector Results

Run ID: 187d9ef3-ebd5-49a8-bc70-c70f24f7a22d

Baseline: f0a8b4c7b06e49a9f97f4067cf2a94cabd1cfbed Comparison: 1f7711fa98bcf154b4ee586b0c959e1be3016667

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 | +1.94 | [+1.84, +2.03] | | | ➖ | dsd_uds_100mb_3k_contexts_distributions_only | memory utilization | +0.12 | [-0.03, +0.28] | | | ➖ | dsd_uds_1mb_3k_contexts | ingress throughput | +0.09 | [+0.03, +0.14] | | | ➖ | dsd_uds_100mb_250k_contexts | ingress throughput | +0.02 | [-0.25, +0.29] | | | ➖ | dsd_uds_1mb_50k_contexts | ingress throughput | +0.02 | [-0.03, +0.06] | | | ➖ | dsd_uds_10mb_3k_contexts | ingress throughput | +0.01 | [-0.08, +0.11] | | | ➖ | dsd_uds_50mb_10k_contexts_no_inlining_no_allocs | ingress throughput | +0.01 | [-0.03, +0.06] | | | ➖ | dsd_uds_100mb_3k_contexts | ingress throughput | +0.00 | [-0.01, +0.01] | | | ➖ | dsd_uds_50mb_10k_contexts_no_inlining | ingress throughput | -0.00 | [-0.00, +0.00] | | | ➖ | dsd_uds_512kb_3k_contexts | ingress throughput | -0.01 | [-0.23, +0.22] | | | ➖ | dsd_uds_1mb_50k_contexts_memlimit | ingress throughput | -1.12 | [-4.41, +2.18] | |

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 3 weeks 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 3 weeks ago

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