markusthoemmes commented on issue #3918: on "application error", return success=false, but should not destroy the container URL: https://github.com/apache/incubator-openwhisk/issues/3918#issuecomment-409021397 I think, on a broader perspective, this might also be related to our general behavior on errors. I think we return 200 for a success and 502 for an error on a blocking invocation. There was a lengthy discussion once whether that should be the case, and whether we should rather see our containers as upstream applications, that, if they returned an error themselves, should be considered successful in the sense that: they didn't crash. We could change that behavior to only return a 502 on a system error (when the platform is at fault) or action-developer error (uncaught/unhandled exceptions), and return a 200 on anything else. Since we have web-actions, you can choose to return fine-grained results anyway if you need them, I don't think we had them back in the day. In the same sense, we would leave containers running that don't cause a system-error or an application-developer error.
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
