-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
innerring: Don't stop the same listener twice #1291
Conversation
When IR node configured without main chain, both `morphListener` and `mainnetListener` are pointing into single listener component. We should not call `Stop()` twice, because it may trigger channel closing in neo-go or other components and it can throw panic. Signed-off-by: Alex Vanin <alexey@nspcc.ru>
Codecov Report
@@ Coverage Diff @@
## master #1291 +/- ##
==========================================
- Coverage 35.48% 35.48% -0.01%
==========================================
Files 310 310
Lines 19234 19238 +4
==========================================
Hits 6826 6826
- Misses 11869 11873 +4
Partials 539 539
Continue to review full report at Codecov.
|
Signed-off-by: Alex Vanin <alexey@nspcc.ru>
do we need that if it gonna be changed in the |
I think there's nothing wrong if you'll have this code. |
When IR node configured without main chain, both `morphListener` and `mainnetListener` are pointing into single listener component. We should not call `Stop()` twice, because it may trigger channel closing in neo-go or other components and it can throw panic. Signed-off-by: Alex Vanin <alexey@nspcc.ru>
Signed-off-by: Alex Vanin <alexey@nspcc.ru>
When IR node configured without main chain, both
morphListener
andmainnetListener
are pointing into single listener component. We should not callStop()
twice, because it may trigger channel closing in neo-go or other components and it can throw panic.Related to nspcc-dev/neo-go#2420