Skip to content
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

Fix INFO response parsing when line breaks are CR-LF #2162

Closed
wants to merge 1 commit into from

Conversation

henry701
Copy link

@henry701 henry701 commented Jul 14, 2022

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 '\'.

I think Windows Redis Fork support is not a critical goal, but the class wasn't using the properties that caused the exception in the first place, so I think this makes sense even as a refactor.

A regression unit test case is included for this change.

Fixes #2161.

refactor: INFO parsing now uses Regular Expressions

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 '\'.
@mp911de mp911de added the type: bug A general bug label Oct 7, 2022
@mp911de mp911de added this to the 6.2.1.RELEASE milestone Oct 7, 2022
@mp911de mp911de changed the title fix: INFO response parsing throws on encountering '\' on NodeTopologyView Fix INFO response parsing when line breaks are CR-LF Oct 7, 2022
mp911de pushed a commit that referenced this pull request 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 added a commit that referenced this pull request Oct 7, 2022
Reformat code. Tweak method names. Reorder method signatures.

Original pull request: #2162.
mp911de pushed a commit that referenced this pull request 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 added a commit that referenced this pull request Oct 7, 2022
Reformat code. Tweak method names. Reorder method signatures.

Original pull request: #2162.
@mp911de
Copy link
Collaborator

mp911de commented Oct 7, 2022

Thank you for your contribution. That's merged, polished, and backported now.

@mp911de mp911de closed this Oct 7, 2022
@mp911de mp911de modified the milestones: 6.2.1.RELEASE, 6.1.10.RELEASE Oct 7, 2022
mp911de pushed a commit that referenced this pull request 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 added a commit that referenced this pull request Oct 7, 2022
Reformat code. Tweak method names. Reorder method signatures.

Original pull request: #2162.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A general bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

INFO response parsing throws on encountering '\' on NodeTopologyView
2 participants