Bug fix: Update the instance variable self.lastDate (not the locally scoped variable lastDate) #9529
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.
Previous to this commit the instance variable
self.lastDatewas not updated as expected in the methodwriteBlock(...)of theBlockDataCopierclass. Instead the locally scoped variablelastDatewas updated.This resulted in
self.lastDatebeing kept constant at its initial valuedatetime.datetime(2000, 1, 1)during the lifetime of theBlockDataCopierobject, which in turn meant that the check ...... was effectively reduced to ...
... since
self.lastDatewas stuck at 2000-01-01.