Bump github.com/aws/aws-lambda-go from 1.37.0 to 1.42.0 #21632
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [github.com/aws/aws-lambda-go](https://github.com/aws/aws-lambda-go) from 1.37.0 to 1.42.0. - [Release notes](https://github.com/aws/aws-lambda-go/releases) - [Commits](aws/aws-lambda-go@v1.37.0...v1.42.0) --- updated-dependencies: - dependency-name: github.com/aws/aws-lambda-go dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
changelog/no-changelog
dependencies
Bloop Bleep... Dogbot HereRegression Detector ResultsRun ID: c16ad286-82d9-4564-9737-d479ffd358d5 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 | confidence |
|---|---|---|---|---|---|
| ➖ | otel_to_otel_logs | ingress throughput | +3.61 | [+2.84, +4.38] | 100.00% |
Declared erratic experiments that are now stable
An experiment is stable (i.e., not erratic) if its coefficient of variation is less than 0.10.
| perf | experiment | goal | Δ mean % | Δ mean % CI | confidence |
|---|---|---|---|---|---|
| ➖ | file_tree | memory utilization | +0.54 | [+0.43, +0.64] | 100.00% |
| ➖ | idle | memory utilization | -0.13 | [-0.15, -0.10] | 100.00% |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | confidence |
|---|---|---|---|---|---|
| ➖ | otel_to_otel_logs | ingress throughput | +3.61 | [+2.84, +4.38] | 100.00% |
| ➖ | process_agent_real_time_mode | memory utilization | +0.59 | [+0.56, +0.62] | 100.00% |
| ➖ | file_tree | memory utilization | +0.54 | [+0.43, +0.64] | 100.00% |
| ➖ | process_agent_standard_check_with_stats | memory utilization | +0.16 | [+0.12, +0.20] | 100.00% |
| ➖ | dogstatsd_string_interner_8MiB_100k | ingress throughput | +0.03 | [+0.02, +0.05] | 99.93% |
| ➖ | trace_agent_json | ingress throughput | +0.02 | [-0.01, +0.05] | 64.29% |
| ➖ | uds_dogstatsd_to_api | ingress throughput | +0.00 | [-0.04, +0.04] | 0.00% |
| ➖ | dogstatsd_string_interner_128MiB_100 | ingress throughput | +0.00 | [-0.05, +0.05] | 0.00% |
| ➖ | dogstatsd_string_interner_8MiB_50k | ingress throughput | +0.00 | [-0.04, +0.04] | 0.00% |
| ➖ | dogstatsd_string_interner_64MiB_1k | ingress throughput | +0.00 | [-0.04, +0.04] | 0.00% |
| ➖ | dogstatsd_string_interner_8MiB_100 | ingress throughput | -0.00 | [-0.04, +0.04] | 0.00% |
| ➖ | dogstatsd_string_interner_8MiB_10k | ingress throughput | -0.00 | [-0.04, +0.04] | 0.00% |
| ➖ | dogstatsd_string_interner_8MiB_1k | ingress throughput | -0.00 | [-0.04, +0.04] | 0.00% |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.06, +0.06] | 0.00% |
| ➖ | dogstatsd_string_interner_128MiB_1k | ingress throughput | -0.00 | [-0.05, +0.05] | 0.00% |
| ➖ | dogstatsd_string_interner_64MiB_100 | ingress throughput | -0.00 | [-0.04, +0.04] | 0.00% |
| ➖ | trace_agent_msgpack | ingress throughput | -0.02 | [-0.04, -0.01] | 96.72% |
| ➖ | idle | memory utilization | -0.13 | [-0.15, -0.10] | 100.00% |
| ➖ | file_to_blackhole | % cpu utilization | -0.16 | [-6.77, +6.45] | 3.16% |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | -0.30 | [-0.36, -0.24] | 100.00% |
| ➖ | process_agent_standard_check | memory utilization | -0.46 | [-0.51, -0.41] | 100.00% |
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".
|
Superseded by #21759. |
dependabot
bot
deleted the
dependabot/go_modules/github.com/aws/aws-lambda-go-1.42.0
branch
Bumps github.com/aws/aws-lambda-go from 1.37.0 to 1.42.0.
Release notes
Sourced from github.com/aws/aws-lambda-go's releases.
... (truncated)
Commits
752114bAdd options lambdaurl.WithDetectContentType and lambda.WithContextValue (#516)1dca084Plumb JSON Decoder options (#515)0ad0619Added Deleted field to support codecommit ref delete events (#531)2ff7818events: add Secrets Manager rotation event (#291) (#530)110afe9Retract v1.39.0 in go.mod (#499)c4e28daAdd "VPC" to .golangci.yml list of initialisms (#526)771b391Changing Headers definition from byte to int8 for KafkaRecord (#506)14212e8feat: add ECSContainerInstanceEvent (#502)5c6579eSupport http.Handler for RESPONSE_STREAM Lambda Function URLs (#503)dc78417test: addtrace_test.go(#497)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions