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 thiserror from 1.0.59 to 1.0.60 #20441
Conversation
Regression Detector ResultsRun ID: 04a13778-c726-43d8-a9d2-828bdf4a7cad Performance changes are noted in the perf column of each table:
Significant changes in experiment optimization goalsConfidence level: 90.00%
|
perf | experiment | goal | Δ mean % | Δ mean % CI |
---|---|---|---|---|
✅ | syslog_humio_logs | ingress throughput | +5.35 | [+5.14, +5.55] |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | +3.31 | [+3.10, +3.51] |
➖ | http_elasticsearch | ingress throughput | +3.02 | [+2.91, +3.12] |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | +2.32 | [+2.15, +2.48] |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | +2.04 | [+1.94, +2.14] |
➖ | fluent_elasticsearch | ingress throughput | +1.20 | [+0.70, +1.69] |
➖ | otlp_grpc_to_blackhole | ingress throughput | +1.15 | [+1.06, +1.25] |
➖ | syslog_loki | ingress throughput | +1.14 | [+1.04, +1.24] |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | +1.04 | [+0.92, +1.16] |
➖ | file_to_blackhole | egress throughput | +0.71 | [-1.90, +3.31] |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | +0.67 | [+0.52, +0.82] |
➖ | syslog_log2metric_humio_metrics | ingress throughput | +0.42 | [+0.26, +0.59] |
➖ | datadog_agent_remap_blackhole | ingress throughput | +0.29 | [+0.14, +0.43] |
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | +0.24 | [+0.02, +0.46] |
➖ | http_to_http_noack | ingress throughput | +0.14 | [+0.06, +0.23] |
➖ | http_to_http_json | ingress throughput | +0.02 | [-0.05, +0.10] |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | +0.00 | [-0.14, +0.15] |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | +0.00 | [-0.14, +0.14] |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | -0.07 | [-0.19, +0.04] |
➖ | http_to_s3 | ingress throughput | -0.12 | [-0.40, +0.16] |
➖ | enterprise_http_to_http | ingress throughput | -0.13 | [-0.21, -0.04] |
➖ | http_to_http_acks | ingress throughput | -0.27 | [-1.62, +1.07] |
➖ | splunk_hec_route_s3 | ingress throughput | -0.29 | [-0.76, +0.17] |
➖ | socket_to_socket_blackhole | ingress throughput | -0.94 | [-1.01, -0.88] |
➖ | http_text_to_http_json | ingress throughput | -1.35 | [-1.54, -1.15] |
➖ | syslog_splunk_hec_logs | ingress throughput | -1.72 | [-1.85, -1.58] |
➖ | otlp_http_to_blackhole | ingress throughput | -3.13 | [-3.29, -2.97] |
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".
Regression Detector ResultsRun ID: 3592b1d2-3d32-41cf-a99a-1d552d5a949c Performance changes are noted in the perf column of each table:
No significant changes in experiment optimization goalsConfidence level: 90.00% There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
|
perf | experiment | goal | Δ mean % | Δ mean % CI |
---|---|---|---|---|
➖ | syslog_log2metric_humio_metrics | ingress throughput | +3.59 | [+3.40, +3.78] |
➖ | splunk_hec_route_s3 | ingress throughput | +1.22 | [+0.76, +1.68] |
➖ | otlp_http_to_blackhole | ingress throughput | +1.13 | [+1.00, +1.27] |
➖ | socket_to_socket_blackhole | ingress throughput | +1.01 | [+0.93, +1.09] |
➖ | http_to_http_acks | ingress throughput | +0.43 | [-0.93, +1.80] |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | +0.24 | [+0.13, +0.35] |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | +0.18 | [+0.06, +0.30] |
➖ | http_to_http_noack | ingress throughput | +0.12 | [+0.01, +0.22] |
➖ | http_text_to_http_json | ingress throughput | +0.07 | [-0.08, +0.21] |
➖ | http_to_http_json | ingress throughput | +0.01 | [-0.06, +0.08] |
➖ | 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.15, +0.15] |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | -0.04 | [-0.16, +0.07] |
➖ | enterprise_http_to_http | ingress throughput | -0.09 | [-0.15, -0.03] |
➖ | http_elasticsearch | ingress throughput | -0.21 | [-0.29, -0.14] |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | -0.26 | [-0.36, -0.17] |
➖ | http_to_s3 | ingress throughput | -0.44 | [-0.72, -0.16] |
➖ | fluent_elasticsearch | ingress throughput | -0.48 | [-0.96, +0.01] |
➖ | datadog_agent_remap_blackhole | ingress throughput | -0.60 | [-0.69, -0.52] |
➖ | otlp_grpc_to_blackhole | ingress throughput | -0.74 | [-0.83, -0.66] |
➖ | file_to_blackhole | egress throughput | -1.47 | [-3.94, +1.01] |
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | -2.42 | [-2.53, -2.30] |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | -2.80 | [-2.93, -2.67] |
➖ | syslog_humio_logs | ingress throughput | -2.85 | [-2.96, -2.75] |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | -3.49 | [-3.64, -3.33] |
➖ | syslog_loki | ingress throughput | -3.77 | [-3.83, -3.71] |
➖ | syslog_splunk_hec_logs | ingress throughput | -4.03 | [-4.13, -3.94] |
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".
Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.59 to 1.0.60. - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](dtolnay/thiserror@1.0.59...1.0.60) --- updated-dependencies: - dependency-name: thiserror dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
a1dab97
to
e87b6b9
Compare
Regression Detector ResultsRun ID: 189415d2-c5d2-490d-a288-d091fbf771a5 Performance changes are noted in the perf column of each table:
No significant changes in experiment optimization goalsConfidence level: 90.00% There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
|
perf | experiment | goal | Δ mean % | Δ mean % CI |
---|---|---|---|---|
➖ | syslog_loki | ingress throughput | +2.71 | [+2.62, +2.81] |
➖ | syslog_log2metric_humio_metrics | ingress throughput | +1.56 | [+1.44, +1.67] |
➖ | datadog_agent_remap_blackhole | ingress throughput | +1.35 | [+1.24, +1.45] |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | +0.97 | [+0.83, +1.10] |
➖ | otlp_grpc_to_blackhole | ingress throughput | +0.45 | [+0.36, +0.54] |
➖ | http_to_http_noack | ingress throughput | +0.18 | [+0.09, +0.27] |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | +0.00 | [-0.15, +0.15] |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | +0.00 | [-0.14, +0.15] |
➖ | http_to_http_json | ingress throughput | -0.00 | [-0.08, +0.07] |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.00 | [-0.14, +0.14] |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | -0.05 | [-0.16, +0.06] |
➖ | enterprise_http_to_http | ingress throughput | -0.06 | [-0.13, +0.01] |
➖ | syslog_humio_logs | ingress throughput | -0.15 | [-0.31, +0.01] |
➖ | file_to_blackhole | egress throughput | -0.16 | [-2.63, +2.32] |
➖ | http_to_s3 | ingress throughput | -0.19 | [-0.47, +0.09] |
➖ | fluent_elasticsearch | ingress throughput | -0.32 | [-0.80, +0.16] |
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | -0.66 | [-0.81, -0.51] |
➖ | http_text_to_http_json | ingress throughput | -0.70 | [-0.85, -0.56] |
➖ | http_to_http_acks | ingress throughput | -0.98 | [-2.33, +0.37] |
➖ | syslog_splunk_hec_logs | ingress throughput | -1.07 | [-1.15, -0.99] |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | -1.08 | [-1.17, -0.99] |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | -1.47 | [-1.60, -1.35] |
➖ | splunk_hec_route_s3 | ingress throughput | -1.60 | [-2.09, -1.11] |
➖ | socket_to_socket_blackhole | ingress throughput | -1.64 | [-1.70, -1.58] |
➖ | otlp_http_to_blackhole | ingress throughput | -2.00 | [-2.12, -1.89] |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | -2.93 | [-3.09, -2.77] |
➖ | http_elasticsearch | ingress throughput | -3.64 | [-3.89, -3.40] |
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".
Regression Detector ResultsRun ID: 8f1c85d4-2ffd-45f5-95bc-114fcc05f232 Performance changes are noted in the perf column of each table:
No significant changes in experiment optimization goalsConfidence level: 90.00% There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
|
perf | experiment | goal | Δ mean % | Δ mean % CI |
---|---|---|---|---|
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | +2.45 | [+2.26, +2.65] |
➖ | syslog_splunk_hec_logs | ingress throughput | +1.67 | [+1.61, +1.72] |
➖ | http_to_http_acks | ingress throughput | +1.41 | [+0.05, +2.78] |
➖ | syslog_loki | ingress throughput | +1.27 | [+1.15, +1.38] |
➖ | http_text_to_http_json | ingress throughput | +1.11 | [+0.96, +1.25] |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | +0.59 | [+0.44, +0.73] |
➖ | otlp_grpc_to_blackhole | ingress throughput | +0.45 | [+0.36, +0.54] |
➖ | syslog_humio_logs | ingress throughput | +0.37 | [+0.20, +0.53] |
➖ | syslog_log2metric_humio_metrics | ingress throughput | +0.27 | [+0.13, +0.41] |
➖ | http_to_http_noack | ingress throughput | +0.17 | [+0.08, +0.25] |
➖ | http_to_http_json | ingress throughput | +0.02 | [-0.05, +0.10] |
➖ | 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.14] |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | -0.00 | [-0.11, +0.10] |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | -0.08 | [-0.20, +0.03] |
➖ | enterprise_http_to_http | ingress throughput | -0.09 | [-0.17, -0.02] |
➖ | datadog_agent_remap_blackhole | ingress throughput | -0.12 | [-0.22, -0.01] |
➖ | http_to_s3 | ingress throughput | -0.25 | [-0.52, +0.03] |
➖ | file_to_blackhole | egress throughput | -0.27 | [-2.87, +2.33] |
➖ | splunk_hec_route_s3 | ingress throughput | -0.41 | [-0.85, +0.04] |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | -0.58 | [-0.66, -0.50] |
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | -0.67 | [-0.84, -0.50] |
➖ | http_elasticsearch | ingress throughput | -0.82 | [-0.90, -0.74] |
➖ | otlp_http_to_blackhole | ingress throughput | -0.84 | [-0.97, -0.71] |
➖ | fluent_elasticsearch | ingress throughput | -1.70 | [-2.19, -1.21] |
➖ | socket_to_socket_blackhole | ingress throughput | -3.87 | [-3.96, -3.78] |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | -4.89 | [-5.01, -4.77] |
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".
Bumps thiserror from 1.0.59 to 1.0.60.
Release notes
Sourced from thiserror's releases.
Commits
870d11b
Release 1.0.600ccee7c
Merge pull request #298 from dtolnay/checkcfgcf43d0c
Resolve unexpected_cfgs warningDependabot 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)