-
Notifications
You must be signed in to change notification settings - Fork 28
Error("data did not match any variant of untagged enum LambdaRequest") #25
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
Comments
Hey @johhnsmmith198 ! Thanks a lot for creating this issue. You're not doing anything wrong. This is an issue between the event that SAM local sends, and the LambdaRequest representation. You can find the related issues here:
And here's the PR to make the Rust runtime more permissive: awslabs/aws-lambda-rust-runtime#366 |
Hey @nmoutschen thanks for the explanation. |
The PR with the fix for this is merged into the main branch for the lambda_http = { git = "https://github.com/awslabs/aws-lambda-rust-runtime/lambda-http" } |
Hey @nmoutschen
I see the log durring build
Still I run sam
and query it simply with
I get the exact same error:
|
Hey @johhnsmmith198 ! I just noticed one issue with your JSON payload: you have two quotes after the {"id"": "i1", "name": "name1", "price": "1"} It should be: {"id": "i1", "name": "name1", "price": "1"} I just tried on my end and it works for me with the Cargo.toml change. |
Thank you very much. What a silly mistake this one. |
Hi Nicolas,
Excellent work thank you so much!
I was trying to run it locally, everything seemed fine but I cannot interact with local sam.
here are the steps that I ran:
-try to insert an item
some resulting logs
What am I doing wrong, please?
Thanks
The text was updated successfully, but these errors were encountered: