Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): Bump nkeys from 0.4.0 to 0.4.1 #20289

Merged
merged 1 commit into from
Apr 19, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Apr 12, 2024

Bumps nkeys from 0.4.0 to 0.4.1.

Commits
  • f105687 chore: bump to 0.4.1
  • 8dbb806 Fix broken CRC handling
  • 333844d chore: drop byteorder dependency
  • 5c4aed3 Merge pull request #29 from protochron/xkey_help
  • df96ac0 fix(cli): mention Curve (xkey) support in the gen command's help text
  • 885294d fix: check length of public key before trying to decode
  • 8e590bf refactor!: change InvalidSeedLength to InvalidKeyLength
  • 2dde3be fix(crc): avoid integer underflow for empty CRC data
  • 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)

Bumps [nkeys](https://github.com/wasmcloud/nkeys) from 0.4.0 to 0.4.1.
- [Release notes](https://github.com/wasmcloud/nkeys/releases)
- [Commits](wasmCloud/nkeys@v0.4.0...v0.4.1)

---
updated-dependencies:
- dependency-name: nkeys
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added domain: deps Anything related to Vector's dependencies no-changelog Changes in this PR do not need user-facing explanations in the release changelog labels Apr 12, 2024
@jszwedko jszwedko added this pull request to the merge queue Apr 19, 2024
Copy link

Regression Detector Results

Run ID: f6024357-2406-418e-b608-9b8a4e49e2a8
Baseline: b451f82
Comparison: f30c9a6
Total CPUs: 7

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.

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI
syslog_humio_logs ingress throughput +2.88 [+2.69, +3.07]
syslog_log2metric_splunk_hec_metrics ingress throughput +2.01 [+1.85, +2.17]
syslog_log2metric_humio_metrics ingress throughput +1.48 [+1.34, +1.63]
datadog_agent_remap_datadog_logs_acks ingress throughput +1.06 [+0.96, +1.16]
datadog_agent_remap_datadog_logs ingress throughput +1.00 [+0.88, +1.11]
file_to_blackhole egress throughput +0.71 [-1.70, +3.12]
datadog_agent_remap_blackhole ingress throughput +0.46 [+0.33, +0.59]
splunk_hec_route_s3 ingress throughput +0.40 [-0.06, +0.86]
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +0.39 [+0.27, +0.52]
http_to_http_noack ingress throughput +0.18 [+0.08, +0.27]
syslog_loki ingress throughput +0.16 [+0.06, +0.25]
http_to_http_json ingress throughput +0.06 [-0.01, +0.14]
syslog_splunk_hec_logs ingress throughput +0.05 [-0.05, +0.16]
splunk_hec_indexer_ack_blackhole ingress throughput -0.00 [-0.15, +0.14]
splunk_hec_to_splunk_hec_logs_acks ingress throughput -0.00 [-0.15, +0.14]
splunk_hec_to_splunk_hec_logs_noack ingress throughput -0.04 [-0.15, +0.08]
enterprise_http_to_http ingress throughput -0.08 [-0.14, -0.01]
http_to_s3 ingress throughput -0.08 [-0.37, +0.20]
otlp_grpc_to_blackhole ingress throughput -0.24 [-0.32, -0.15]
http_elasticsearch ingress throughput -0.52 [-0.62, -0.43]
http_to_http_acks ingress throughput -0.72 [-2.07, +0.63]
http_text_to_http_json ingress throughput -1.42 [-1.54, -1.29]
datadog_agent_remap_blackhole_acks ingress throughput -1.75 [-1.89, -1.61]
socket_to_socket_blackhole ingress throughput -1.85 [-1.93, -1.77]
otlp_http_to_blackhole ingress throughput -2.13 [-2.28, -1.99]
fluent_elasticsearch ingress throughput -2.32 [-2.79, -1.84]
syslog_regex_logs2metric_ddmetrics ingress throughput -3.06 [-3.20, -2.93]

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

Copy link

Regression Detector Results

Run ID: c96fb06d-0a9f-4ad3-b725-3ef753809e1c
Baseline: 32dedb4
Comparison: 9e03021
Total CPUs: 7

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.

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI
datadog_agent_remap_blackhole_acks ingress throughput +2.66 [+2.55, +2.77]
syslog_humio_logs ingress throughput +2.27 [+2.15, +2.38]
datadog_agent_remap_datadog_logs ingress throughput +1.08 [+0.95, +1.21]
http_to_http_acks ingress throughput +0.84 [-0.52, +2.20]
file_to_blackhole egress throughput +0.73 [-1.82, +3.28]
syslog_loki ingress throughput +0.66 [+0.60, +0.72]
syslog_splunk_hec_logs ingress throughput +0.63 [+0.58, +0.67]
datadog_agent_remap_datadog_logs_acks ingress throughput +0.59 [+0.51, +0.67]
socket_to_socket_blackhole ingress throughput +0.55 [+0.49, +0.61]
datadog_agent_remap_blackhole ingress throughput +0.47 [+0.38, +0.55]
syslog_log2metric_humio_metrics ingress throughput +0.33 [+0.21, +0.45]
http_elasticsearch ingress throughput +0.19 [+0.11, +0.27]
http_to_http_noack ingress throughput +0.07 [-0.04, +0.17]
http_to_http_json ingress throughput +0.03 [-0.04, +0.11]
splunk_hec_to_splunk_hec_logs_acks ingress throughput +0.00 [-0.14, +0.14]
splunk_hec_indexer_ack_blackhole ingress throughput +0.00 [-0.14, +0.15]
splunk_hec_to_splunk_hec_logs_noack ingress throughput -0.04 [-0.15, +0.08]
enterprise_http_to_http ingress throughput -0.06 [-0.12, +0.01]
syslog_log2metric_splunk_hec_metrics ingress throughput -0.21 [-0.36, -0.06]
syslog_regex_logs2metric_ddmetrics ingress throughput -0.26 [-0.40, -0.13]
otlp_grpc_to_blackhole ingress throughput -0.47 [-0.56, -0.38]
splunk_hec_route_s3 ingress throughput -0.47 [-0.92, -0.02]
http_to_s3 ingress throughput -0.48 [-0.76, -0.19]
otlp_http_to_blackhole ingress throughput -0.75 [-0.88, -0.61]
fluent_elasticsearch ingress throughput -1.13 [-1.61, -0.66]
http_text_to_http_json ingress throughput -2.16 [-2.33, -2.00]
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput -2.97 [-3.11, -2.84]

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

Merged via the queue into master with commit 9e03021 Apr 19, 2024
56 checks passed
@jszwedko jszwedko deleted the dependabot/cargo/nkeys-0.4.1 branch April 19, 2024 22:38
AndrooTheChen pushed a commit to discord/vector that referenced this pull request Sep 23, 2024
Bumps [nkeys](https://github.com/wasmcloud/nkeys) from 0.4.0 to 0.4.1.
- [Release notes](https://github.com/wasmcloud/nkeys/releases)
- [Commits](wasmCloud/nkeys@v0.4.0...v0.4.1)

---
updated-dependencies:
- dependency-name: nkeys
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain: deps Anything related to Vector's dependencies no-changelog Changes in this PR do not need user-facing explanations in the release changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant