Remove timeout if stream datum takes too long to be produced #74
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.
This removes a hard coded timeout that otherwise gets raised if stream datums take too long to be produced. Unfortunately this timeout actually captures the gap between the final stream datum of a previous fly scan collection point, and the next stream datum - this can take an indefinite amount of time, probably set by the flyer triggering period (or a similar metric).
There is another branch (stall-timeout) where I am trying to work on this issue. For now, this timeout is erroneous and should be removed.