issue warning when external script is not executable?
Posted: January 13th, 2019, 5:46 pm
Hello,
I've just been caught-out by this again.
I'm trying a new external Python post-processing script, and I forgot to set the executable bits on it. I was able to select this script via the SAB UI but SAB didn't complain until it attempted to run the script. It then told me the script wasn't executable.
Would it be possible for SAB to issue a logged warning message when a non-executable script has been selected for a queue item? Maybe this could happen everytime a new queue item is added, or an existing queue item changes post-processing to use an unexecutable script?
Thank you.
I've just been caught-out by this again.
I'm trying a new external Python post-processing script, and I forgot to set the executable bits on it. I was able to select this script via the SAB UI but SAB didn't complain until it attempted to run the script. It then told me the script wasn't executable.
Would it be possible for SAB to issue a logged warning message when a non-executable script has been selected for a queue item? Maybe this could happen everytime a new queue item is added, or an existing queue item changes post-processing to use an unexecutable script?
Thank you.