mgencur edited a comment on issue #3941: to address #3918, reuse a container on applicationError URL: https://github.com/apache/incubator-openwhisk/pull/3941#issuecomment-412000192 Hi, I'm wondering what's the rationale behind throwing different types of errors when there's a timeout during init and run phases. Some thoughts: * how is timeout during initialization different from the timeout during run that we want to treat it differently? * can the timeout during init be caused by something else than a developer writing the function in a wrong way? * when I look at the code and the variables it makes sense: ContainerError during init phase and ApplicationError during run phase, but then later the ContainerError translates to "action developer error" which starts to get confusing * if we want to treat init and run timeouts differently should we also have an option to set different timeouts for these phases? * anyway, I'd vote for simplicity - one timeout, one type of error, it gets a little too complicated Thanks
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
