[GitHub] tardieu commented on issue #3966: Conductor action returns "application error" when continuation function throws an uncaught exception

[GitBox <gi...@apache.org>]

tardieu commented on issue #3966: Conductor action returns "application error" when continuation function throws an uncaught exception
URL: https://github.com/apache/incubator-openwhisk/issues/3966#issuecomment-420693051
 
 
   In the current implementation, the conductor action only sees the result of the composed action, not the full response. Application errors and action developer errors are represented in the same ambiguous way: a json dictionary with a single error field. The conductor action therefore cannot propagate the precise status. The "conductor.js" code used here (https://github.com/apache/incubator-openwhisk/blob/master/tests/dat/actions/conductor.js#L9) unconditionally reports an "application error" in all cases. Alternatively, the code `if (args.error) throw args.error` would unconditionally produce an "action developer error".
   
   I am thinking of introducing support for "raw" conductor actions, where the full response would be made available to the conductor action, but the code for this does not exist yet.
   
   In the documentation, "invocation failure" is intended to mean an internal error at invocation time, not an unsuccessful invocation with an "action developer error" or an "application error". I'll update the documentation to be clearer.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services