Introduce PROCESSINFO_TRIGGERMODE_SEMAPHORE_PROP_TIMEOUTS and make it… #35
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… default for milk-streamFITSlog.
Adding triggermode 5, which is also a semaphore mode.
In triggermode
PROCESSINFO_TRIGGERMODE_SEMAPHORE
(==3), the TIMEOUT is caught and the overall computation is shunted into acontinue;
In
PROCESSINFO_TRIGGERMODE_SEMAPHORE_PROP_TIMEOUTS
(==5), the timeout is willfully propagated, the execution of the loop iteration begins, and the timeout status can be checked in processinfo if need be. This actually emulates the old semaphore behavior when timeouts would propagate (by default every second) and click the AO chain unit after unit.This fixes the following issues in logshim:
@oguyon foresee any pitfall?