"socket hang up" error when running "sls run" for more than 2 minutes.

[vincentsolutions]

Every time I'm trying to sls run a service that takes more than 2 minutes to load the functions, I receive a socket hang up error that stops my function loading. Often, if I have a sls run window that is already running, it will load the functions in that window, but it'll hang up before those functions are registered.

From my investigations, I think that this is caused by the fact that the plain node child-process that emulator spawns has a default server timeout of 2 minutes, so whenever I'm trying to sls run services for more than 2 minutes, the timeout occurs, and I get the socket hang up error.

I think that #4 could fix this if there was a timeout config param that we could set. But maybe there's an easier/quicker solution to this without having to implement a config system?

[iksnae]

anything new on this. i'm this issue consistently now.