Fix HGETDEL FIELDS token validation - #4049
Merged
Merged
Conversation
Signed-off-by: lcxn123 <156999965+lcxn123@users.noreply.github.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthrough
ChangesHGETDEL syntax validation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related issues
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
roshkhatri
self-requested a review
June 24, 2026 20:54
Member
Can you please look at the failing test? the change seems okay |
roshkhatri
self-requested a review
June 24, 2026 22:48
Signed-off-by: lcxn123 <156999965+lcxn123@users.noreply.github.com>
Co-authored-by: Binbin <binloveplay1314@qq.com> Signed-off-by: lcxn123 <156999965+lcxn123@users.noreply.github.com>
Signed-off-by: lcxn123 <156999965+lcxn123@users.noreply.github.com>
valkeyrie-ops Bot
pushed a commit
that referenced
this pull request
Jun 26, 2026
Add explicit validation for the FIELDS token before parsing numfields. Fixes #4045. Signed-off-by: lcxn123 <156999965+lcxn123@users.noreply.github.com> Co-authored-by: Binbin <binloveplay1314@qq.com>
vansvan17
pushed a commit
to vansvan17/valkey
that referenced
this pull request
Jul 9, 2026
Add explicit validation for the FIELDS token before parsing numfields. Fixes valkey-io#4045. Signed-off-by: lcxn123 <156999965+lcxn123@users.noreply.github.com> Co-authored-by: Binbin <binloveplay1314@qq.com> Signed-off-by: Vanshika <vanshikaturakhia@gmail.com>
sarthakaggarwal97
pushed a commit
that referenced
this pull request
Jul 14, 2026
Add explicit validation for the FIELDS token before parsing numfields. Fixes #4045. Signed-off-by: lcxn123 <156999965+lcxn123@users.noreply.github.com> Co-authored-by: Binbin <binloveplay1314@qq.com>
alon-arenberg
pushed a commit
to alon-arenberg/valkey
that referenced
this pull request
Jul 15, 2026
Add explicit validation for the FIELDS token before parsing numfields. Fixes valkey-io#4045. Signed-off-by: lcxn123 <156999965+lcxn123@users.noreply.github.com> Co-authored-by: Binbin <binloveplay1314@qq.com> Signed-off-by: Alon Arenberg <alonare@amazon.com>
alon-arenberg
pushed a commit
to alon-arenberg/valkey
that referenced
this pull request
Jul 30, 2026
Add explicit validation for the FIELDS token before parsing numfields. Fixes valkey-io#4045. Signed-off-by: lcxn123 <156999965+lcxn123@users.noreply.github.com> Co-authored-by: Binbin <binloveplay1314@qq.com> Signed-off-by: Alon Arenberg <alonare@amazon.com>
enjoy-binbin
pushed a commit
that referenced
this pull request
Aug 3, 2026
) #4049 fixed the FIELDS token validation for `HGETDEL`. The same parsing issue also exists in `HPERSIST` and `HTTL/HPTTL/HEXPIRETIME/HPEXPIRETIME`: The `FIELDS` keyword was never validated, so a malformed command like `HPERSIST key a 1 c` would silently treat `a` as a no-op and parse the remaining arguments instead of returning a syntax error. This PR aligns these commands with the HGETDEL fix: reject the command with a syntax error when the `FIELDS` keyword is missing, and adds tests covering the validation for all affected commands. Signed-off-by: cjx-zar <jxchenczar@foxmail.com>
valkeyrie-ops Bot
pushed a commit
that referenced
this pull request
Aug 3, 2026
) #4049 fixed the FIELDS token validation for `HGETDEL`. The same parsing issue also exists in `HPERSIST` and `HTTL/HPTTL/HEXPIRETIME/HPEXPIRETIME`: The `FIELDS` keyword was never validated, so a malformed command like `HPERSIST key a 1 c` would silently treat `a` as a no-op and parse the remaining arguments instead of returning a syntax error. This PR aligns these commands with the HGETDEL fix: reject the command with a syntax error when the `FIELDS` keyword is missing, and adds tests covering the validation for all affected commands. Signed-off-by: cjx-zar <jxchenczar@foxmail.com>
valkeyrie-ops Bot
pushed a commit
that referenced
this pull request
Aug 3, 2026
) #4049 fixed the FIELDS token validation for `HGETDEL`. The same parsing issue also exists in `HPERSIST` and `HTTL/HPTTL/HEXPIRETIME/HPEXPIRETIME`: The `FIELDS` keyword was never validated, so a malformed command like `HPERSIST key a 1 c` would silently treat `a` as a no-op and parse the remaining arguments instead of returning a syntax error. This PR aligns these commands with the HGETDEL fix: reject the command with a syntax error when the `FIELDS` keyword is missing, and adds tests covering the validation for all affected commands. Signed-off-by: cjx-zar <jxchenczar@foxmail.com>
valkeyrie-ops Bot
pushed a commit
that referenced
this pull request
Aug 16, 2026
) #4049 fixed the FIELDS token validation for `HGETDEL`. The same parsing issue also exists in `HPERSIST` and `HTTL/HPTTL/HEXPIRETIME/HPEXPIRETIME`: The `FIELDS` keyword was never validated, so a malformed command like `HPERSIST key a 1 c` would silently treat `a` as a no-op and parse the remaining arguments instead of returning a syntax error. This PR aligns these commands with the HGETDEL fix: reject the command with a syntax error when the `FIELDS` keyword is missing, and adds tests covering the validation for all affected commands. Signed-off-by: cjx-zar <jxchenczar@foxmail.com>
valkeyrie-ops Bot
pushed a commit
that referenced
this pull request
Aug 18, 2026
) #4049 fixed the FIELDS token validation for `HGETDEL`. The same parsing issue also exists in `HPERSIST` and `HTTL/HPTTL/HEXPIRETIME/HPEXPIRETIME`: The `FIELDS` keyword was never validated, so a malformed command like `HPERSIST key a 1 c` would silently treat `a` as a no-op and parse the remaining arguments instead of returning a syntax error. This PR aligns these commands with the HGETDEL fix: reject the command with a syntax error when the `FIELDS` keyword is missing, and adds tests covering the validation for all affected commands. Signed-off-by: cjx-zar <jxchenczar@foxmail.com>
valkeyrie-ops Bot
pushed a commit
that referenced
this pull request
Aug 20, 2026
) #4049 fixed the FIELDS token validation for `HGETDEL`. The same parsing issue also exists in `HPERSIST` and `HTTL/HPTTL/HEXPIRETIME/HPEXPIRETIME`: The `FIELDS` keyword was never validated, so a malformed command like `HPERSIST key a 1 c` would silently treat `a` as a no-op and parse the remaining arguments instead of returning a syntax error. This PR aligns these commands with the HGETDEL fix: reject the command with a syntax error when the `FIELDS` keyword is missing, and adds tests covering the validation for all affected commands. Signed-off-by: cjx-zar <jxchenczar@foxmail.com>
sarthakaggarwal97
pushed a commit
that referenced
this pull request
Aug 30, 2026
) #4049 fixed the FIELDS token validation for `HGETDEL`. The same parsing issue also exists in `HPERSIST` and `HTTL/HPTTL/HEXPIRETIME/HPEXPIRETIME`: The `FIELDS` keyword was never validated, so a malformed command like `HPERSIST key a 1 c` would silently treat `a` as a no-op and parse the remaining arguments instead of returning a syntax error. This PR aligns these commands with the HGETDEL fix: reject the command with a syntax error when the `FIELDS` keyword is missing, and adds tests covering the validation for all affected commands. Signed-off-by: cjx-zar <jxchenczar@foxmail.com>
sarthakaggarwal97
pushed a commit
that referenced
this pull request
Aug 30, 2026
) #4049 fixed the FIELDS token validation for `HGETDEL`. The same parsing issue also exists in `HPERSIST` and `HTTL/HPTTL/HEXPIRETIME/HPEXPIRETIME`: The `FIELDS` keyword was never validated, so a malformed command like `HPERSIST key a 1 c` would silently treat `a` as a no-op and parse the remaining arguments instead of returning a syntax error. This PR aligns these commands with the HGETDEL fix: reject the command with a syntax error when the `FIELDS` keyword is missing, and adds tests covering the validation for all affected commands. Signed-off-by: cjx-zar <jxchenczar@foxmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add explicit validation for the FIELDS token before parsing numfields.
Fixes #4045.