Marc Bachmann

That's how blocking queries work in redis. If you use `BLOCK 0` in combination with `xread`, it won't be possible to call `xadd` as the connection is in use by...

pipelining isn't multiplexing, so redis can't handle two commands simultaneously on the same connection. As best practice, use one global redis instance, which is only used by non-blocking queries. And...

Should we just update the documentation about that or copy the scripts over?

We could also think about extending the prototype of the main redis instance. This would be similar to what's been asked in https://github.com/luin/ioredis/issues/1410 ``` // root instance doesn't inherit scripts,...

The scripts support in the config looks good and that way it gets inherited. 👍 Let's document the current behavior of `.duplicate()`

> I added Redis Stream Classes. Maybe they help you That's not relevant at all Regarding the issue. There's a slot table: https://github.com/luin/ioredis/blob/88b8a3125cd039afdac928c529a1b9958009979c/test/functional/cluster/transaction.ts#L9-L12 https://github.com/luin/ioredis/blob/88b8a3125cd039afdac928c529a1b9958009979c/lib/cluster/index.ts#L850 And some way to calculate it...

hmm, a force push merged this accidentally and can't reopen. I'll merge this manually

hah. reopen button shows up again. edit: nope. didn't work

Released as v1.22.0

In ioredis I've solved this by caching script load information using a weakmap against the socket: https://github.com/redis/ioredis/blob/ec42c82ceab1957db00c5175dfe37348f1856a93/lib/Script.ts#L29-L36 Whenever a custom script command gets execute, it uses either `eval` or `evalsha`.