Don't wait for new data when override_night set in daily_proc_manager #1866
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.
A small change to prevent unnecessary waiting at the end of desi_daily_proc_manager when being run on previous night's data using over_ride night. In
main
it waits 300 seconds at the end of each iteration. In this PR it waits 300 seconds after each iteration unless override_night is set and a debugging flag is not set.I tested this by running with override_night set and with it unset and the proper behavior is observed in each instance. This is small enough that I will self merge.