Fix load balancing heuristics, make load balancer public #36
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fixes the load balancing heuristics that were broken in e6e6d85#diff-d4a68aa4a4bea23eaf6314456bacd52dd00b3c0e9b7275669c3ac627eb6deefb
It also makes the load balancer publicly accessible, such that the functioning of the load balancer can be observed. This is a feature that I relied upon in my old Lavalink-Client. I fixed the heuristics on top of the first changes, and I was not inclined to go out of my way to separate them.
P.S: While cherry-picking, the master branch tripped me up. May want to delete that.