Skip to content

Fix parsing of INFO response #3264

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
Jun 5, 2024
Merged

Conversation

gerzse
Copy link
Contributor

@gerzse gerzse commented Jun 5, 2024

If the INFO response contains a single a=b value for any of the keys, that must also be parsed into a dictionary.

Fixes #3262

Pull Request check-list

Please make sure to review and check all of these items:

  • Do tests and lints pass with this change?
  • Do the CI tests pass with this change (enable it first in your forked repo and wait for the github action build to finish)?
  • Is the new or changed code fully tested?
  • Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
  • Is there an example added to the examples folder (if applicable)?
  • Was the change added to CHANGES file?

NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.

Description of change

Please provide a description of the change here.

If the INFO response contains a single `a=b` value for any of the keys,
that must also be parsed into a dictionary.

Fixes redis#3262
@gerzse gerzse added the bug Bug label Jun 5, 2024
@gerzse gerzse requested a review from dvora-h June 5, 2024 10:10
@gerzse gerzse merged commit 26d2d13 into redis:5.0 Jun 5, 2024
53 checks passed
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants