João Miguel Neves
João Miguel Neves
@nabazm I think your case is just a repeat of #1638
I'm keeping this one open, because the damned message is not clear (and I hope to sort it out). I think I've fixed the problem with the "slim_handler: true" error...
No, it was part of an unlocking of the dependencies to identify cases like this (where we had version dependencies that were not documented/surfaced because we had them all pinned....
This requirement was made explicit with 0.51.0, but I'm keeping this issue open until we update the code to be compatible with werkzeug 1.0.0.
How are you measuring the cold starts? It seems like you're moving the initialisation into the importing phase of the code, so I wouldn't expect it to be faster on...
This is solved by #1998 which I hope to merge and release this week. And we should be done with pinned dependencies altogether.
Not yet, haven't found the specific reason why it was locked in the first place. Will have to check if it's just some API change.
Thanks, will hopefully sort this out tomorrow.
@uuqq thanks - would I need just a lambda with an ALB to replicate the problem? If not, can you share a sample config?
Do you have any region field in the AWS config or credentials files and/or any value (or empty string) on an environment variable called AWS_REGION?