Closed slifty closed 3 years ago
Merging this without approval despite the critical bug it introduces. Also creating an issue to reflect that memory leak.
The reasoning for this terrible terrible choice is that I don't think the memory leak will cause critical failure at this stage in the project's life, whereas the out of order payloads will. That being said, we have to fix the memory leak before we can say this is a tool that others can use.
Description
This PR fixes CountertopWorker so that it will not write to Kafka until the previous payload has been processed.
Due Diligence Checklist
Steps to Test
yarn test
Deploy Notes
None
Related Issues
Resolves #110