[BUG] Traceability panic error memory address runtime al2023

Open
#559 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, go
Domain
backend, cloud

Research direction

Start by reproducing a panic in a Go Lambda using the provider.al2023 runtime and compare its logs with the go1.x runtime. Investigate how the panic and memory-address error are surfaced; done means the al2023 runtime reports the underlying panic and line number instead of only the generic Runtime.Unknown message.

Written by the indexing model from the issue text.

Description

Since changing the runtime of our lambdas from go1.x to provider.al2023, I'm encountering a problem with the traceability of panic error memory logs.
Instead of

invalid memory address or nil pointer dereference

and the line number where it stops, I have:

calling the handler function resulted in a panic, the process should exit
Unknown application error occurred Runtime.Unknown

This message appears on all my functions with the "provider.al2023" runtime.

Thanks.

Dominant language
Go
Stars
3.8k
Forks
578
Avg merge
16h 56m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/aws-lambda-go

All issues in aws/aws-lambda-go

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.