We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Just abstract example:
(async f1() { const client1 = asyncRedis.createClient(); await client1.blpop("some", 0); })() (async f2() { const client2 = asyncRedis.createClient(); await client2.lpush("some", 42); })()
f2's lpush will never be called as client1 and client2 share same connection due to new implementation
The text was updated successfully, but these errors were encountered:
duplicated of #60 :p
Sorry, something went wrong.
an workaround:
(async f1() { const client1 = asyncRedis.createClient({ _id: 1 }); await client1.blpop("some", 0); })() (async f2() { const client2 = asyncRedis.createClient({ _id: 2 }); await client2.lpush("some", 42); })()
you must pass different options for each client.
No branches or pull requests
Just abstract example:
f2's lpush will never be called as client1 and client2 share same connection due to new implementation
The text was updated successfully, but these errors were encountered: