This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
Connector creates too many ws connections with the node which stresses out the node #1981
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
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## development #1981 +/- ##
============================================
Coverage 68.10% 68.11%
============================================
Files 299 299
Lines 5318 5319 +1
Branches 975 975
============================================
+ Hits 3622 3623 +1
Misses 1696 1696
|
…e connection liveness
vardan10
force-pushed
the
1978-Connector-creates-too-many-ws-connections-with-the-node-which-stresses-out-the-node
branch
from
b9efc4b to
1a95c33
Compare
priojeetpriyom
approved these changes
Dec 11, 2023
priojeetpriyom
deleted the
1978-Connector-creates-too-many-ws-connections-with-the-node-which-stresses-out-the-node
branch
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 was the problem?
This PR resolves #1978
How was it solved?
How was it tested?
Local