Closed andresvia closed 4 years ago
Hmmm, yep I can see how that happened – I've unified all runtimes to use the same API for error reporting, and I had never noticed that Java had this field before (I don't think any of the other runtimes do).
Should have a chance to figure out the best fix for this in a couple of hours 👍
For C# is explicit in the docs: https://docs.aws.amazon.com/lambda/latest/dg/dotnet-exceptions.html
Some blog post mention it: https://aws.amazon.com/blogs/compute/redirection-in-a-serverless-api-with-aws-lambda-and-amazon-api-gateway/
I had fun.
Truedat! I'm using the custom runtime API and it doesn't mention it – but I'll add it
https://docs.aws.amazon.com/lambda/latest/dg/runtimes-api.html#runtimes-api-invokeerror
Have pushed the new images with this fix – thanks for reporting!
Coming from twitter: https://twitter.com/hichaelmart/status/1197986958955483136?s=20
Given this code:
And these docker images:
The image with hash
9f97c1886601d56fdd0599ecc66910dc6ac88ccfea5386ab70cd931edf5d7b96
includes the "cause" in the error, but the newerdea85f569727d89c7eb8767658cc0dada73ddb9a90fafd570a2c28def893d16a
does not.New image pull and run:
Old "backup" image:
Thank you @mhart , you are doing a terrific job!