issue warning when external script is not executable?

[OneCD]

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.

[safihre]

Sure, we can do that. Let me check.

[safihre]

Oke maybe it's harder than I thought, since post-proc scripts are set in multiple places.

[OneCD]

Thanks @safihre.

What if the choice of listed scripts shows only the executable ones? Then the user wouldn’t be able to select a non-executable script.

[safihre]

That would be possible, but would that not be confusing?

[OneCD]

Well, it may lead to support questions like “why can’t SABnzbd see my script?”

Then my first question would be “is it executable?”