-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Bump github.com/aws/aws-sdk-go-v2/service/secretsmanager from 1.31.1 to 1.33.1 #29523
base: main
Are you sure you want to change the base?
Bump github.com/aws/aws-sdk-go-v2/service/secretsmanager from 1.31.1 to 1.33.1 #29523
Conversation
Bumps [github.com/aws/aws-sdk-go-v2/service/secretsmanager](https://github.com/aws/aws-sdk-go-v2) from 1.31.1 to 1.33.1. - [Release notes](https://github.com/aws/aws-sdk-go-v2/releases) - [Changelog](https://github.com/aws/aws-sdk-go-v2/blob/service/s3/v1.33.1/CHANGELOG.md) - [Commits](aws/aws-sdk-go-v2@service/s3/v1.31.1...service/s3/v1.33.1) --- updated-dependencies: - dependency-name: github.com/aws/aws-sdk-go-v2/service/secretsmanager dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Go Package Import DifferencesBaseline: be76ade
|
Regression DetectorRegression Detector ResultsRun ID: 003265b9-c6bc-4a95-889d-8d34ff31d644 Metrics dashboard Target profiles Baseline: be76ade 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 | trials | links |
---|---|---|---|---|---|---|
➖ | otel_to_otel_logs | ingress throughput | +0.72 | [-0.09, +1.53] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.17 | [-0.58, +0.91] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.00 | [-0.07, +0.08] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.01, +0.01] | 1 | Logs |
➖ | basic_py_check | % cpu utilization | -0.19 | [-2.88, +2.50] | 1 | Logs |
➖ | idle | memory utilization | -0.28 | [-0.33, -0.23] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | -0.43 | [-0.47, -0.38] | 1 | Logs |
➖ | file_tree | memory utilization | -0.52 | [-0.61, -0.43] | 1 | Logs |
➖ | pycheck_lots_of_tags | % cpu utilization | -1.49 | [-4.00, +1.03] | 1 | Logs |
Bounds Checks
perf | experiment | bounds_check_name | replicates_passed |
---|---|---|---|
✅ | idle | memory_usage | 10/10 |
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 github.com/aws/aws-sdk-go-v2/service/secretsmanager from 1.31.1 to 1.33.1.
Changelog
Sourced from github.com/aws/aws-sdk-go-v2/service/secretsmanager's changelog.
... (truncated)
Commits
ae835ec
Release 2023-05-04ef7f367
Regenerated Clientsa62e494
Update endpoints model833592f
Update API model829131f
Add SQSCustomizations (#2108)9d08e7d
Release 2023-05-03cec4d55
Regenerated Clientsf558c81
Update API model8d2e554
Release 2023-05-02312e442
Regenerated ClientsDependabot 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)