datadog-agent icon indicating copy to clipboard operation
datadog-agent copied to clipboard

Bump github.com/swaggest/jsonschema-go from 0.3.64 to 0.3.70

Open dependabot[bot] opened this issue 1 year ago • 2 comments
trafficstars

Bumps github.com/swaggest/jsonschema-go from 0.3.64 to 0.3.70.

Release notes

Sourced from github.com/swaggest/jsonschema-go's releases.

v0.3.70

What's Changed

Full Changelog: https://github.com/swaggest/jsonschema-go/compare/v0.3.69...v0.3.70

v0.3.69

What's Changed

Full Changelog: https://github.com/swaggest/jsonschema-go/compare/v0.3.68...v0.3.69

v0.3.68

What's Changed

Full Changelog: https://github.com/swaggest/jsonschema-go/compare/v0.3.67...v0.3.68

v0.3.67

What's Changed

Full Changelog: https://github.com/swaggest/jsonschema-go/compare/v0.3.66...v0.3.67

v0.3.66

What's Changed

Full Changelog: https://github.com/swaggest/jsonschema-go/compare/v0.3.65...v0.3.66

v0.3.65

What's Changed

Full Changelog: https://github.com/swaggest/jsonschema-go/compare/v0.3.64...v0.3.65

Commits
  • 524f24b Improve example inferring with JSON support and type cohesion (#114)
  • 9575eb9 Improve interface assertions to allow val/ptr receivers without data loss (#112)
  • fbc1e0d Fix value method call on nil pointer (#111)
  • 2d5f6b0 Fix default parsing (#110)
  • 57ddbd6 Skip def name for a func type that may return different schemas (#109)
  • ee6e1be Use type string for encoding.TextMarshaler (#108)
  • 8eee225 Optionally expose embedded structs with allOf (#107)
  • 04e0738 Update CI (#106)
  • 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 <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)

dependabot[bot] avatar Mar 13 '24 18:03 dependabot[bot]

Test changes on VM

Use this command from test-infra-definitions to manually test this PR changes on a VM:

inv create-vm --pipeline-id=30050071 --os-family=ubuntu

pr-commenter[bot] avatar Mar 13 '24 19:03 pr-commenter[bot]

Regression Detector

Regression Detector Results

Run ID: 1367d268-2463-4aa2-b3e1-be9c9fae9e04 Baseline: f868170b123898186b1eac1491d35f71d94a808b Comparison: 7ab25ccd67d5f7d08db8d21dd73dd029bcc5d337

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
file_to_blackhole % cpu utilization -0.95 [-6.57, +4.66]

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI
file_tree memory utilization +1.50 [+1.36, +1.64]
basic_py_check % cpu utilization +1.05 [-1.50, +3.60]
otel_to_otel_logs ingress throughput +0.40 [-0.05, +0.84]
process_agent_standard_check memory utilization +0.18 [+0.13, +0.23]
process_agent_real_time_mode memory utilization +0.12 [+0.07, +0.16]
trace_agent_msgpack ingress throughput +0.01 [+0.00, +0.03]
uds_dogstatsd_to_api ingress throughput +0.00 [-0.20, +0.20]
trace_agent_json ingress throughput +0.00 [-0.01, +0.01]
tcp_dd_logs_filter_exclude ingress throughput -0.00 [-0.04, +0.03]
tcp_syslog_to_blackhole ingress throughput -0.02 [-0.12, +0.07]
process_agent_standard_check_with_stats memory utilization -0.07 [-0.12, -0.01]
pycheck_1000_100byte_tags % cpu utilization -0.30 [-5.23, +4.64]
uds_dogstatsd_to_api_cpu % cpu utilization -0.31 [-3.26, +2.64]
idle memory utilization -0.47 [-0.50, -0.43]
file_to_blackhole % cpu utilization -0.95 [-6.57, +4.66]

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] avatar Mar 13 '24 20:03 pr-commenter[bot]

@dependabot rebase

paulcacheux avatar Jun 19 '24 07:06 paulcacheux

/merge

paulcacheux avatar Jun 19 '24 07:06 paulcacheux

:steam_locomotive: MergeQueue: waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals. Note: if you pushed new commits since the last approval, you may need additional approval. You can remove it from the waiting list with /remove command.

Use /merge -c to cancel this operation!

dd-devflow[bot] avatar Jun 19 '24 07:06 dd-devflow[bot]

:steam_locomotive: MergeQueue: pull request added to the queue

The median merge time in main is 27m.

Use /merge -c to cancel this operation!

dd-devflow[bot] avatar Jun 19 '24 09:06 dd-devflow[bot]