vector
vector copied to clipboard
chore(deps): bump async-nats to v0.35
Closes #20008
Thanks @paolobarbolini . I suspect this will need some more changes though since clippy failed on the other upgrade to v0.34. I kicked off CI to see. Locally you can run make check-clippy.
Regression Detector Results
Run ID: 0193fe57-be2f-4ef3-a489-1d7427e7ec28 Baseline: 911e63d4ee35c1de5082b6c2df6bc4ac0678ff31 Comparison: 5ca291fff5f1d8f62aab8ac73997919238b0509b 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_log2metric_tag_cardinality_limit_blackhole | ingress throughput | +4.56 | [+4.44, +4.69] |
| ➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | +4.12 | [+3.98, +4.27] |
| ➖ | syslog_splunk_hec_logs | ingress throughput | +3.58 | [+3.47, +3.68] |
| ➖ | syslog_humio_logs | ingress throughput | +3.01 | [+2.90, +3.13] |
| ➖ | syslog_loki | ingress throughput | +2.53 | [+2.42, +2.63] |
| ➖ | splunk_hec_route_s3 | ingress throughput | +1.28 | [+0.81, +1.76] |
| ➖ | syslog_log2metric_humio_metrics | ingress throughput | +1.11 | [+0.96, +1.26] |
| ➖ | socket_to_socket_blackhole | ingress throughput | +1.08 | [+0.98, +1.17] |
| ➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | +0.51 | [+0.37, +0.65] |
| ➖ | otlp_grpc_to_blackhole | ingress throughput | +0.38 | [+0.28, +0.47] |
| ➖ | datadog_agent_remap_blackhole_acks | ingress throughput | +0.29 | [+0.19, +0.38] |
| ➖ | http_text_to_http_json | ingress throughput | +0.27 | [+0.14, +0.40] |
| ➖ | http_to_http_acks | ingress throughput | +0.23 | [-1.14, +1.60] |
| ➖ | datadog_agent_remap_blackhole | ingress throughput | +0.22 | [+0.11, +0.33] |
| ➖ | datadog_agent_remap_datadog_logs | ingress throughput | +0.18 | [+0.07, +0.29] |
| ➖ | http_to_s3 | ingress throughput | +0.17 | [-0.11, +0.45] |
| ➖ | fluent_elasticsearch | ingress throughput | +0.15 | [-0.33, +0.62] |
| ➖ | http_to_http_noack | ingress throughput | +0.07 | [-0.02, +0.15] |
| ➖ | http_to_http_json | ingress throughput | +0.04 | [-0.04, +0.11] |
| ➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.00 | [-0.15, +0.14] |
| ➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | -0.01 | [-0.15, +0.14] |
| ➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | -0.04 | [-0.16, +0.07] |
| ➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | -0.05 | [-0.14, +0.05] |
| ➖ | enterprise_http_to_http | ingress throughput | -0.09 | [-0.18, -0.00] |
| ➖ | http_elasticsearch | ingress throughput | -0.59 | [-0.66, -0.52] |
| ➖ | file_to_blackhole | egress throughput | -1.46 | [-3.94, +1.02] |
| ➖ | otlp_http_to_blackhole | ingress throughput | -2.06 | [-2.20, -1.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:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
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.
-
Its configuration does not mark it "erratic".
It looks like some tests failed because of the nkeys 0.4.1 upgrade. https://github.com/wasmCloud/nkeys/pull/31 fixed some broken nkey verification logic which was also wrong in tests. I guess this project may have the same issue too. I'll get back to this in a few days.
Closing in favor of #21504