Fix failing lambda error reporting test #12300
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
With recent updates to
public.ecr.aws/lambda/python:3.12
it seems AWS ships a newer Lambda RIC client with those images than they use in AWS.This leads to a disparity between the stacktrace returned by aws, and the one in LS.
As the stack trace line numbers are not really important to get exactly right, for me that is a reasonable compromise for now (other option would be pinning the images).
For now I have skipped the stack trace check - we should check in the future to unskip it once AWS incorporates the changes in their environment as well.
Changes