Exit transformer on target process exit#395
Merged
edgurgel merged 1 commit intoedgurgel:masterfrom Oct 1, 2019
Merged
Conversation
Owner
|
I like this approach as it should not impact current users of the async requests 👍 Thank you for the PR! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When making an asynchronous response, if the target process dies (or is killed) there is no purpose in the transformer process still continuing to run, so we should kill this also.
This is a simple fix that I believe partially solves #375 . An alternative would be to allow the target process to kill the transformer in some way by sending it a message, but I think the approach in this PR is safer.