You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wasted about 8 hours to investigate the root cause of this problem. I could not find any documents.
At least please write compatibility note about node.js runtime on documentation for customers.
The text was updated successfully, but these errors were encountered:
Sorry about the inconvenience. We are in a testing process with the new Lambda 8.10 runtime to see what works, what breaks and what needs to be done to fix the issues. We will have our doc team soon post a note in our user guide about the current SDK doesn't work with the new async handler.
I successfully reproduced the issue with the example you gave. I'm closing this in favor of #27 so we all have a single place to share updates/findings/fixes.
We will continue to look at 8.10 support and will update #27 as soon as we have any new update.
I've found super annoying issue after migrating to nodejs8.10 runtime with async handler.
Short Reproducible code
Expected Result
Lambda Execution result should be
{ data: "oh my!" }
.Actual Result
On lambda nodejs8.10 runtime: returns
null
.On native node 8.10 docker image: returns
{ data: "oh my!" }
If comment
require("aws-xray-sdk-core")
line, lambda nodejs8.10 runtime returns expected{ data: "oh my!" }
.I wasted about 8 hours to investigate the root cause of this problem. I could not find any documents.
At least please write compatibility note about node.js runtime on documentation for customers.
The text was updated successfully, but these errors were encountered: