Skip to content
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

callBuffer does not work with auto-pipelining enabled. #1923

Open
Sophos-Elias-Vasylenko opened this issue Oct 15, 2024 · 0 comments
Open

callBuffer does not work with auto-pipelining enabled. #1923

Sophos-Elias-Vasylenko opened this issue Oct 15, 2024 · 0 comments

Comments

@Sophos-Elias-Vasylenko
Copy link

Sophos-Elias-Vasylenko commented Oct 15, 2024

Simple to reproduce. Open a client with auto-pipelining, and do something like await client.callBuffer("eval", "return 'Hello, scripting!'", 0) or just await client.callBuffer("get", "wizard")

You will get an error like ReplyError: ERR unknown command 'return 'Hello, scripting!'', with args beginning with: '0'

It works properly if you use call instead of callBuffer. Seems like something fishy is probably happening in this vicinity with all the shuffling around of arguments

return executeWithAutoPipelining(

Not had time to investigate further.

Work-around is to add the failing commands to the auto pipelining exclude list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant