This repository has been archived by the owner on Aug 2, 2021. It is now read-only.
network: terminate Hive connect goroutine on Stop #1740
Merged
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 PR addresses the issue where Hive connect goroutine does not exit after calling Hive.Stop(), creating goroutone leaks. It appears that it was expected for Hive.ticker.C to be closed after Hive.ticker.Stop() is called, but that is not the case. Ticker channel is not closed leaving the for loop waiting indefinitely as no more ticks are sent.
This issue can be reproduced with this network ad hoc test: