gresau / rocket-lamb Goto Github PK

Thanks for a great project, I have been using it for a few simple lambdas. Running into a small issue though.

When running my server locally I am able to get stdout fine, but when deployed the CW logs do not show any of it (just the Lambda system messages). Any ideas on how to address that?

I know that Rocket 0.5 is still in development but I was wondering if you had any thoughts about how to support it? It brings with it async support via Tokio 1.0 which (as far as I know) will be incompatible with the current lambda_runtime crate. In other projects I've been using netlify_lambda which is a fork of the official project that's been updated for Tokio 1.0, so maybe that's a good option?

I don't know what else is changing with Rocket 0.5 that might disrupt things, but I'm happy to take a swing at making it work. I mostly just wanted to check in to see if you have plans to / a strategy for supporting it.

When running a rocket-lamb application via sam local start-api then attempting to call the function via curl http://127.0.0.1:3000/ I am getting a response of {"message":"Internal server error"} with several Error: Response headers do not contain Lambda-Runtime-Invoked-Function-Arn header in the logs.

To Reproduce

1. Clone https://github.com/GREsau/example-rocket-lamb-api
2. Run docker-compose run --rm build
3. Run sam local start-api

Other Info

1. I tried this on my own project first and got the same result, then tried out the example assuming something was wrong. Locally I cross-compile to x86_64-unknown-linux-musl from macOS whereas the example uses a containerized build.
2. Platform: macOS 11.1 x86_64 (not ARM)
3. I did not have softprops/lambda-rust locally so it pulled the latest on run
4. Rust version: 1.51.0-nightly (bc39d4d9c 2021-01-15)
5. SAM CLI version: 1.15.0 (installed via Homebrew)

Let me know if there is any other info I can provide that would be useful!

I'm deploying my function the way this example does. Is it possible to deploy the container itself, now that AWS Lambda supports containers?

When too many database connections are started, Diesel produces this error:

[ERROR r2d2] Too many connections

The problem is, that this error is being spammed hundreds of times, until the lambda function times out, after which it starts another function, which immediately gives the same error, looping again and again.

This has happened 15 times in 3 seconds, after which it stopped (somehow). The server stops functioning completely at this point, until I redeploy it.

The reason I'm submitting this here is that I have only ever seen this issue when running the application on Lambda, and the error handling is fatal.

There are no examples using async, such as tokio.

Would I be able to use this with async libs?