-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
getBuffer returns string when enableAutoPipelining is true #1228
Comments
Been looking into this a bit further and seems to be caused by *Buffer commands being created with Buffer omitted commands.forEach(function (commandName) {
Commander.prototype[commandName] = generateFunction(commandName, "utf8");
Commander.prototype[commandName + "Buffer"] = generateFunction(
commandName,
null
);
}); This ...
// Create a new pipeline and make sure it's scheduled
return executeWithAutoPipelining(this, commandName, args, callback);
}; At which point the context that it's the Buffer variant of the command (and encoding is null) is lost. |
cc @ShogunPanda |
I checked the PR. It LGTM! |
+1 |
Hi, firstly, thanks for releasing the new auto pipelining feature.
Whilst testing on my project, I noticed that
getBuffer
returns the result converted to string (rather than aBuffer
) withenableAutoPipelining
set totrue
. Is this expected/ a known limitation with the pipelining implementation?The text was updated successfully, but these errors were encountered: