-
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
fix(cluster): make blocking commands works with cluster #867
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you need to raise the PR on the latest build I can see there is some code changes with this version to the latest one such as timeout is not moved to utils_1 folder.
@manasa-ei It seems this commit was made on top of the latest commit:
Do I miss anything? |
@luin Seems working fine with this fix. My bad I didn't check properly, yes the push is on latest commit. Please go ahead and merge it. |
🎉 This PR is included in version 4.9.5 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Awesome, thanks! |
## [4.9.5](redis/ioredis@v4.9.4...v4.9.5) (2019-05-15) ### Bug Fixes * **cluster:** make blocking commands works with cluster ([#867](redis/ioredis#867)) ([68db71b](redis/ioredis@68db71b)), closes [#850](redis/ioredis#850) [#850](redis/ioredis#850)
As discussed in #850, we should use a separate connection for refreshing slots to avoid conflict with blocking commands invoked by users.
There are three tests failed in these changes. Still need some investigations.