add simple fix to set farmer response timer for SP: 0
#13655
Merged
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.
The farmer response timer was not set for a sub-slot, so the farmer response times for
SP: 0
was always calculated compared to the node start time (like described in issues #11869, #10900).This PR simply sets the current timer for
signage_point_times[0]
for everyFinished sub slot
, similar like it is done for every signage point.Tested this PR for a day and this is how the log entry looks like for
SP: 0
: