Implements a degraded state detection for LavalinkClusterNode #180
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.
When the socket looses the connection to node, clustered node status should became Degraded. When connection established again, status should return back to Available.
I'm actually doesn't quite happy with the implementation, since
SocketConnectionReady
kinda duplicates already existent ready task in socket, but at the moment when socket fires the ConnectionClosed, LavalinkNode doesn't recreate the ready TaskCompletitionSource yet, so awaiting it in cluster node will be immediately completed.