-
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
Fix/Handle chain notifications via pool #1653
Fix/Handle chain notifications via pool #1653
Conversation
Handling notification in a synchronous manner may lead to a blocking state if a handler uses neo-go client. Signed-off-by: Pavel Karpy <carpawell@nspcc.ru>
Codecov Report
@@ Coverage Diff @@
## master #1653 +/- ##
==========================================
- Coverage 33.18% 33.13% -0.05%
==========================================
Files 332 332
Lines 22706 22707 +1
==========================================
- Hits 7536 7525 -11
- Misses 14552 14564 +12
Partials 618 618
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couldn't freeze node with this fix
Fix commit message please |
@KirillovDenis, wrong push. The second commit should be merged via #1656. Fixed. |
Handling notification in a synchronous manner may lead to a blocking state if a handler uses neo-go client. Signed-off-by: Pavel Karpy <carpawell@nspcc.ru>
Related to #1577. Fixes node freezing but does not affect the problem with a call timeout.