Bryan Marty

You may also need the following permissions for zappa to setup SNS event handling: SNS:ListSubscriptionsByTopic SNS:Unsubscribe SNS:Subscribe

Yes, re-deploying the code fixed it. I encountered this before, and I think another way I fixed it was by re-saving the function in the LAMBDA console. I could get...

@Miserlou Can we add a line after https://github.com/Miserlou/Zappa/blob/master/zappa/handler.py#L506. so that it looks like: ``` print(e) print(traceback.format_exc(e)) ``` I see that the exec info is in the HTTP response when only...

It happened again today. Doing the above, I got the following traceback: ``` 1492967445091] 'NoneType' object is not callable [1492967445091] Traceback (most recent call last): [1492967445091] File "/var/task/handler.py", line 450,...

@darrell-rg However in my case, it happens without "zappa update". The code will be running fine on production, as packaged, then in a few days, I will encounter this error.

@darrell-rg If AWS is, they are doing it randomly, because it work in the beginning. It would say that must be a pretty remote chance tho. One suspicion is some...

I too turned off slim_handler, and the issue hasn't happened again.

@GeorgianaPetria Make sure your excluding any directories or files you don't need, like any build artifacts, node_modules, static/, vendor/, images, etc. Also remove any unneeded packages from your virtual environment

In my case, I don't have any build scripts On Sep 11, 2017 9:40 AM, "darrell-rg" wrote: > Finally found the cause of my issue. A build script that ran...

Fwiw: the 50mb limit is somewhat soft. I have uploaded packages as large as 60mb. I'm not sure what the real, enforced cut off is. I adopted a microservice methodology,...