-
Notifications
You must be signed in to change notification settings - Fork 139
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
fix(logger): fix clearstate bug when lambda handler throws #1045
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the fix! Left one comment in the unit tests.
…state functionality
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for addressing the comments!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
I have one suggestion but it's subjective opinion on readability.
…ctLambdaContextAfterOrOnError function behaviour - separation of concerns
Description of your changes
This PR introduces a bug fix for issue #1027.
Previously, when using
addPersistentLogAttributes
orappendKeys
and an error was thrown inside the Lambda handler function, the clear state functionality did not work.This PR includes the business logic fix and updated unit tests.
How to verify this change
See checks passing, including e2e tests run.
Related issues, RFCs
Issue number: #1027
PR status
Is this ready for review?: YES
Is it a breaking change?: NO
Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.