Fix LSET listpack conversion after element replacement#3985
Conversation
|
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 (2)
📝 WalkthroughWalkthrough
ChangesLSET encoding conversion fix
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 |
Signed-off-by: Taeknology <20297177+Taeknology@users.noreply.github.com>
57812ef to
67e0a28
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## unstable #3985 +/- ##
============================================
+ Coverage 76.63% 76.71% +0.08%
============================================
Files 162 162
Lines 80788 80790 +2
============================================
+ Hits 61909 61978 +69
+ Misses 18879 18812 -67
🚀 New features to boost your workflow:
|
Issue
LSETreplaces an existing list element, but the old conversion check treated the new value like an appended element. Withlist-max-listpack-size 3, replacing one small value in a 3-element listpack could wrongly convert it to quicklist.Fixes #2162.
Changes
LSETreplaces the element.Tests
make -C src valkey-server -j$(nproc)./runtest --single tests/unit/type/list.tcl(291 passed, 0 failed)git diff --check