aws / aws/aws-lambda-base-images

Python 3.10 Lambda image throws Segmentation Violation when running locally

Open
#100 6 comments 11 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
777
Forks
118
PR merge metrics
No merged PRs in 30d

Description

Any lambda image release for 3.10 past `public.ecr.aws/lambda/python:3.10.2023.05.07.17` cause the following error on receipt of a post request to the test endpoint when running locally

```
23 May 2023 23:13:20,652 [DEBUG] (rapid) invoke: -> POST /2015-03-31/functions/function/invocations map[Accept:[*/*] Accept-Encoding:[gzip, deflate] Baggage:[...] Connection:[keep-alive] Content-Length:[34] Content-Type:[application/json] Sentry-Trace:[...] User-Agent:[python-requests/2.28.2]]
23 May 2023 23:13:20,652 [INFO] (rapid) ReserveFailed: AlreadyReserved
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x68c30f]

goroutine 68 [running]:
go.amzn.com/lambda/rapidcore.(*Server).Invoke.func2()
/LambdaRuntimeLocal/lambda/rapidcore/server.go:653 +0xef
created by go.amzn.com/lambda/rapidcore.(*Server).Invoke
/LambdaRuntimeLocal/lambda/rapidcore/server.go:636 +0x23d
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.