We've seen some errors recently where acu.generate_scan doesn't run properly within a seq.scan call. This PR introduces an internal check_started function, similar to the other "check" functions, which is meant to be called immediately after a <process>.start() call is made. It'll wait for the operation state to go from 'starting' to 'running', and raise an exception if that doesn't happen.
For SMuRFs starting their 'stream' process, if this occurs that SMuRF will be removed from the targets list, much like if a single task were to fail for a given SMuRF, up to the configured threshold of failures.
We've seen some errors recently where
acu.generate_scandoesn't run properly within aseq.scancall. This PR introduces an internalcheck_startedfunction, similar to the other "check" functions, which is meant to be called immediately after a<process>.start()call is made. It'll wait for the operation state to go from 'starting' to 'running', and raise an exception if that doesn't happen.For SMuRFs starting their 'stream' process, if this occurs that SMuRF will be removed from the targets list, much like if a single task were to fail for a given SMuRF, up to the configured threshold of failures.
Resolves #56.