Closed DirkRusche-Otto closed 2 months ago
Thanks for the clear description and steps to reproduce the problem. https://github.com/awslabs/aws-lambda-rust-runtime/pull/892 should fix it.
This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one.
Thank you for the quick fix, very appreciated.
Can you give me an ETA of when this fix will be released to cargo?
Can you give me an ETA of when this fix will be released to cargo?
Probably this week. You can fetch the code from GitHub meanwhile.
I noticed that starting with version
0.11.0
an error from a handler is no longer printed and not sent to CloudWatch logs.The PR #845 states:
Reading this comment I guess the change in behavior is expected. In case of an error, debugging the Lambda becomes way harder since there is no log message why and even that the Lambda failed.
Is there already a solution how to get the old behavior (error being logged) back?
How to reproduce
Example code
Example code to reproduce the issue
Version
>=0.11.0
If I run it with (for example) version
0.11.2
and the commandscargo lambda watch
andcargo lambda invoke --data-ascii "{}"
gives me the output:Version
0.10.0
If I run it with version
0.10.0
I see the error: