Skip to content

Convert the value to int type only if it exists in CLIENT INFO #3688

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

Merged
merged 3 commits into from
Jul 11, 2025

Conversation

git-hulk
Copy link
Contributor

@git-hulk git-hulk commented Jun 30, 2025

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)?

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

Description of change

Currently, client info will try to convert the set of keys to the int type without checking if it exists or not. To keep compatibility with newer Redis servers or other Redis-compatible services, we could just convert it only if the key exists.

git-hulk and others added 3 commits June 30, 2025 20:34
Currently, client info will try to convert the set of keys to the int type
without checking if it exists or not. For example, both `argv-mem` and `tot-mem`
are introduced in 6.2, and force converting an non-existent value might
cause an exception in older version. To keep the compatibility with the older/newer
Redis server, we could just convert it only if the key exists.
@petyaslavova petyaslavova added the maintenance Maintenance (CI, Releases, etc) label Jul 10, 2025
@petyaslavova
Copy link
Collaborator

Hi @git-hulk, apologies for the delayed response. I rebased your PR and will merge it tomorrow.

@git-hulk
Copy link
Contributor Author

@petyaslavova Thank you! I see one of CI is broke but it's related to upload the artifact and not relate to the current fix. Should I worry about this.

@petyaslavova
Copy link
Collaborator

@petyaslavova Thank you! I see one of CI is broke but it's related to upload the artifact and not relate to the current fix. Should I worry about this.

@git-hulk No worries, it happens quite often lately. I restarted that job.

@petyaslavova petyaslavova merged commit ce56d1c into redis:master Jul 11, 2025
67 of 68 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Maintenance (CI, Releases, etc)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants