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.

Sign up for GitHub

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

Jump to bottom

Garbage data returned by getBuffer when enableAutoPipelining is set to true. #1356

Closed
rahbaner opened this issue May 20, 2021 · 2 comments
Closed

Garbage data returned by getBuffer when enableAutoPipelining is set to true. #1356

rahbaner opened this issue May 20, 2021 · 2 comments

Comments

@rahbaner
Copy link

rahbaner commented May 20, 2021 •
edited
Loading

It has been observed that when enableAutoPipelining is set to true, getBuffer returns garbage data. When I set enableAutoPipelining to false, getBuffer returns proper data.

Would it be possible to have a look at this? Looks like PR #1231 fixes this. Can this be merged if it look ok @luin ? If there is an alternate way you plan to fix this, that is also perfectly fine. Just needed to for reducing load on redis cluster (so that I dont need to do JSON.stringify on compressed data before setting it to redis.).
@luin
Copy link
Collaborator

luin commented May 22, 2021

Closed via #1231. Thanks for the heads up!

@luin luin closed this as completed May 22, 2021
@rahbaner
Copy link
Author

Thanks a lot @luin. This indeed works fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@luin @rahbaner