Ensure that CombinedProcessor reinitializes self.combined_maintenance_data #86
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.
Fixes #85
The root cause was that for CombinedProcessor,
self.combined_maintenance_data
was only initialized at class instantiation time, meaning that when processing a second set of data using the same processor, any keys previously set onself.combined_maintenance_data
would bleed over from one processing to the next. The solution is to reinitialize this dictionary each timeprocess()
is called.