Increase lambda deployment timeout?

[jonapich]

I had to raise botocore/endpoint.py/DEFAULT_TIMEOUT manually in order to succeed in pushing my lambda function.

[jamesls]

Interesting. Out of curiosity what value did you have to change it to?

[jonapich]

120 (out of frustration) ;)

…

On May 23, 2017 1:45 PM, "James Saryerwinnie" ***@***.***> wrote: Interesting. Out of curiosity what value did you have to change it to? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#344 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AExvzLVI8cB346JrvIOyTDvCOA6HPsLyks5r8xYhgaJpZM4NhZqF> .

[rerngvit]

I have precisely the same problem. I got "Connection aborted. Timed out sending your app to Lambda.", repeatedly, when trying to do "chalice deploy". It would be great, if a command line option to specify timeout is available.

[zjost]

Same problem here. This started happening when I added numpy/pandas to my requirements.txt, so presumably it has something to do with bundling that up and sending it. Also confirming that changing botocore/endpoint.py/DEFAULT_TIMEOUT to 120 worked.

[nplutt]

Hey @jamesls, I started working on this and was wondering if you like the idea of allowing this to be configured through an option in the deploy command. I was imagining something like:

$ chalice deploy --botocore-timeout 120

After the timeout value is consumed by the cli I was thinking about changing the CLIFactory class so that a botocore_timeout value can be set and modified.

[lenards]

When this is available, I believe they settled on --connection-timeout in #629, based on the additions in commit eafa12975

However, at the time of this post, I think this in master and not up on pypi yet.

✘-1 ~/gh/tableflipless [master L|✚ 2…7] 
08:54 $ pipenv run chalice deploy --botocore-timeout 145
Error: no such option: --botocore-timeout
✘-2 ~/gh/tableflipless [master L|✚ 2…7] 
08:56 $ pipenv run chalice deploy --connection-timeout 145
Error: no such option: --connection-timeout
✘-2 ~/gh/tableflipless [master L|✚ 2…7] 
08:56 $ pipenv run chalice deploy --connection-timeout=140
Error: no such option: --connection-timeout

With chalice==1.1.0

[nplutt]

You are correct, if you look at the change log this feature will be released with the next release which is currently TBD.

[lenards]

Cool, thanks!

I just wanted to tag this issue with the command flag that was used so if someone lands here from a search, they got it.

[moneroexamples]

Not the change timeout command is:

chalice deploy --connection-timeout 120