-
Notifications
You must be signed in to change notification settings - Fork 215
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: add timeout to protocol notifications + log improvements #3143
fix: add timeout to protocol notifications + log improvements #3143
Conversation
dd228a0
to
d01b3dd
Compare
d01b3dd
to
817304e
Compare
PR queued successfully. Your position in queue is: 2 |
PR is on top of the queue now |
PR failed to merge with reason: Some CI status(es) failed |
PR queued successfully. Your position in queue is: 2 |
PR is on top of the queue now |
PR failed to merge with reason: Some CI status(es) failed |
PR queued successfully. Your position in queue is: 1 |
PR failed to merge with reason: Some CI status(es) failed |
PR queued successfully. Your position in queue is: 2 |
PR is on top of the queue now |
PR failed to merge with reason: Some CI status(es) failed |
PR queued successfully. Your position in queue is: 1 |
PR failed to merge with reason: Some CI status(es) failed |
7d2ca09
to
5585f58
Compare
- protocol notifications now have a set "safety" timeout. - add log for inbound comms pipeline concurrency usage
5585f58
to
a98a698
Compare
Waiting for approval before queuing |
Description
Motivation and Context
Reports of inbound messaging being blocked. This will shed some light.
The logs show that a single client node is excessively trying to create multiple
t/bn-wallet//1
(rpc) sessions.How Has This Been Tested?
Log observed in base node
Checklist:
development
branch.