Jean Boussier

I'm about to release a 5.0, so that would be the occasion to change this. I'll sleep on it though.

Closing as stale. Either way I think the `ring:` parameter is enough, users can pass their own ring implementation, which is good enough for adavanced usages and much more flexible...

@brauliobo what connector are you using? Hiredis or the regular "Ruby" one?

Not particularly, but I ask because I've tried to reproduce that problem multiple time with no success, and the previous maintainer tried too without success either. The patch you used,...

> We need a new redis connection on every API request. That of course generates a lot of redis connections, specially under load Sure, but, I did try to craft...

So that doesn't help figuring the connection leak, but I just skimmed at https://github.com/dv/redis-semaphore/blob/master/lib/redis/semaphore.rb and I don't see any blocking call or anything else that would requires to have a...

This is fixed on master (upcoming 5.0). If either `host`, `port` or `path` is passed `$REDIS_URL` is ignored.

> So, it would be awhile before we can deprecate this gem 🙊 I'm currently working on `redis-rb` 5.0, which will use `redis-client` under the hood. Once it's done `hiredis-rb`...

The blockless transaction support is removed in 5.0, so closing this as no longer relevant.

I didn't expect people to still be using this to be honest. There really isn't one replacement for it. If you really want the same behavior, you can use `$redis`...