You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if root scripts fail multiple times, the run will stop, however if a user script fails, the run will keep going.
This is could be problematic for environments that need the user section to complete successfully. With 5218c96 I fixed the infinite looping when not exiting 0, but introduced this issue.
This will be a difficult one to solve since the user side runs in a different process and we cannot capture the state of the run itself.
The text was updated successfully, but these errors were encountered:
Currently, I've been unloading IA's LaunchDaemon from within the user script if it fails. That method is less than ideal and requires some hacking.
An idea (haven't tested this):
Perhaps after iaslog('Failed to run user script!') in 5218c96 we could drop another artifact (eg. touch a file)?
Then, in the IA main process, when the while os.path.isfile(userscripttouchpath): process breaks, we could check if that artifact is present and stop the run there?
if root scripts fail multiple times, the run will stop, however if a user script fails, the run will keep going.
This is could be problematic for environments that need the user section to complete successfully. With 5218c96 I fixed the infinite looping when not exiting 0, but introduced this issue.
This will be a difficult one to solve since the user side runs in a different process and we cannot capture the state of the run itself.
The text was updated successfully, but these errors were encountered: