[PR] [EXEC-121] Fail fast async execution for non-existing executable [commons-exec]

["Marcono1234 (via GitHub)" <gi...@apache.org>]

Marcono1234 opened a new pull request, #144:
URL: https://github.com/apache/commons-exec/pull/144

   This also has the side effect of ensuring that the process destroyer, if any, is registered.
   
   Have marked this as draft for now because I am not sure if this a good solution. It causes the following behavior differences (which might be acceptable though):
   - Longer delay for async execution because calling thread now has to wait until process is started
   - Fail-fast behavior might be unexpected for caller; might expect that failure is reported through `ExecuteStreamHandler`
   
   Maybe the race condition reported in EXEC-121 could also be solved differently by having another shutdown hook which verifies that all processes are started and their process destroyers (if any) have been registered. Though this logic might be quite complicated.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@commons.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org