-
Notifications
You must be signed in to change notification settings - Fork 992
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
INFO response parsing throws on encountering '\' on NodeTopologyView #2161
Labels
type: bug
A general bug
Milestone
Comments
mp911de
pushed a commit
that referenced
this issue
Oct 7, 2022
INFO command parsing inside NodeTopologyView used to throw when encountering '\' characters due to the use of the Java Property parser. This happens when using some Redis on Windows forks due to the Windows path separator being '\'. Original pull request: #2162.
mp911de
pushed a commit
that referenced
this issue
Oct 7, 2022
INFO command parsing inside NodeTopologyView used to throw when encountering '\' characters due to the use of the Java Property parser. This happens when using some Redis on Windows forks due to the Windows path separator being '\'. Original pull request: #2162.
mp911de
pushed a commit
that referenced
this issue
Oct 7, 2022
INFO command parsing inside NodeTopologyView used to throw when encountering '\' characters due to the use of the Java Property parser. This happens when using some Redis on Windows forks due to the Windows path separator being '\'. Original pull request: #2162.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
INFO command parsing inside NodeTopologyView throws when encountering '\' characters due to the use of the Java Property parser. This happens when using some Redis on Windows forks due to the Windows path separator being '\'.
Current Behavior
Exception is thrown when connecting to a Redis Cluster where the INFO command has Windows paths.
Stack trace:
Input Code
Input Code
Expected behavior/code
No exception is thrown and the INFO command output is parsed without issue
Environment
Possible Solution
Pull request #2162
The text was updated successfully, but these errors were encountered: