-
Notifications
You must be signed in to change notification settings - Fork 32
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
Guides on AWS Lambda s3 event fails with micronaut 4.2.2, 4.2.3 : An error occurred during JSON parsing: java.lang.RuntimeException #1410
Comments
marcpa00
changed the title
Guides on AWS Lambda s3 event fails with micronaut 4.2.3 : An error occurred during JSON parsing: java.lang.RuntimeException
Guides on AWS Lambda s3 event fails with micronaut 4.2.2 : An error occurred during JSON parsing: java.lang.RuntimeException
Jan 6, 2024
Just noticed the downloaded zip uses micronaut 4.2.2; will change for 4.2.3 and report back if issue is still there. |
Verified with micronaut 4.2.3 : same outcome (but stack trace sightly different)
Result is :
|
I tried to add SerdeImport annotations as suggested in stack trace to no avail.
Stack trace :
|
marcpa00
changed the title
Guides on AWS Lambda s3 event fails with micronaut 4.2.2 : An error occurred during JSON parsing: java.lang.RuntimeException
Guides on AWS Lambda s3 event fails with micronaut 4.2.2, 4.2.3 : An error occurred during JSON parsing: java.lang.RuntimeException
Jan 6, 2024
Note that trying to use Jackson serialization by adding the jackson-databind dependency does not work either. Modified dependencies in gradle.build :
Result:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using the completed example zip (https://guides.micronaut.io/latest/micronaut-aws-lambda-s3-event-gradle-java.zip) (2024-01-06, micronaut 4.2.2) and following the instructions in https://guides.micronaut.io/latest/micronaut-aws-lambda-s3-event-gradle-java.html to create aws bucket, role, lambda function with appropriate trigger, produced the stack trace (full log in csv attached) :
log-events-viewer-result.csv
The text was updated successfully, but these errors were encountered: