Handle empty addresses in CLUSTER NODES
responses
#148
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 parsing a
CLUSTER NODES
response we will now treat an empty IP string as it means the same endpoint as the response came from. This due to that the docs mention that an empty string is returned for the IP field when the node doesn't know its own IP address.The created
valkeyClusterNode
will get its address from thevalkeyContext
used when sending the command.Additional changes are that we will use the
noaddr
flag instead of the address length when deciding when a node should be skipped; and added validation of the port.Example of a response snippet with an empty address:
"752d150249c157c7cb312b6b056517bbbecb42d2 :6379@16379 myself,master - 1658754833817 1658754833000 3 connected 5461-10922"