Fixed processors to use appropriate config #55
Closed
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.
This is a WIP, buthoping to get some eyes on it as a fix for #54.We're currently using the subscriber config for all asynchronous processing, even in spots where we should be using the publisher config. This changes the behavior and implementation of processors to make them instantiable classes that accept the config they should be working with. I also introduced a new
Pool
module that is responsible for tracking all async processors and flushing properly. (Need to add tests for this still.)