This repository has been archived by the owner on Feb 16, 2020. It is now read-only.
Finish candleloader on empty data, fix #2457 #2475
Merged
Conversation
This file contains 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
added 2 commits
August 21, 2018 14:54
Sometimes child.kill() failes. Better disconnect the parent and let the child exit itself.
|
👍 thanks. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
bugfix.
What is the current behavior? (You can also link to an open issue here)
Still getting sometimes node processes of candleLoader which never get killed. If reader data is empty than DONE never set to true and there is an infinite loop.
What is the new behavior (if this is a feature change)?
Now checking if iterator.from is > than "to" and ending the candleLaoder.
Other information: