-
Notifications
You must be signed in to change notification settings - Fork 39
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
Wrongly parsed redis::response when executing MULTI statement #210
Comments
Modifying
Edit: Not using MULTI/EXEC and putting everything into one request also seems to work fine.
|
Hi, thanks for reporting. I will have a look at it on this weekend. For now you could check if the |
mzimbres
added a commit
that referenced
this issue
Oct 5, 2024
mzimbres
added a commit
that referenced
this issue
Oct 6, 2024
mzimbres
added a commit
that referenced
this issue
Oct 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Let me preface the bug report that I may be doing something horribly wrong and misusing the library.
Now that thats out of the way, lets start off at redis/redis-cli level and lower the description of the observation towards the output seen in C++ and at the very end is the code sample that replicates this behavior.
Lets create a dummy test set
SADD TEST_SET a b c d e f g
redis-cli output
And intersect it with a temporary set that contains the values a and z.
redis-cli output
Everything looks fine and this works when translated into the same C++ code. The issue starts when the intersection is empty as the follow up command response is parsed to the member representing SDIFF.
redis-cli output
The result of the SDIFF operator when I translate the above two MULTI transactions into boost/redis is as follows:
Appreciate any feedback as to what I am doing wrong. Changing the type to either
std::set<std::string>
orstd::optional<std::vector<std::string>>
gives the same behavior.Code:
The text was updated successfully, but these errors were encountered: