Resque: The client method is deprecated as of redis-rb 4.0.0, please use the new _clientmethod instead. Support for the old method will be removed in redis-namespace 2.0.

[huuth]

Everything is working fine, but the message "The client method is deprecated as of redis-rb 4.0.0, please use the new _clientmethod instead. Support for the old method will be removed in redis-namespace 2.0." always dispayed in terminal console.

Please explain or help me fix it. Thanks

[henrik]

@huuth You can probably work around it by downgrading the redis-rb gem to version 3. In your Gemfile:

gem "redis", "<4"

Then run bundle update redis.

Or wait for Resque to be updated, or make a pull request :)

It seems redis-rb has removed or renamed some methods that Resque uses: https://github.com/redis/redis-rb/blob/master/CHANGELOG.md#40

[Fjool]

This warning originates in redis-namespace:

https://github.com/resque/redis-namespace/blob/master/lib/redis/namespace.rb

It is supposed to be possible to disable the warnings during config, but this one doesn't test "warning?". Should be simple enough to correct.

[spilth]

Any timeline for a release with this fix?

[jeremy]

No timeline, @spilth. Other than Real Soon Now 😍

[joshuabaird]

Still looking at "real soon?" :)

[jeremy]

_Real_ Soon Now 🤐

[vruizext]

I had to monkey-patch Redis::Namespace in my initializer as a workaround, until the fix is released

Redis::Namespace.class_eval do
  def client
    _client
  end
end

[CodingAnarchy]

Any update? Not sure why this is closed when it is still an issue a year later.

[rafaelfranca]

This is already fixed on the master branch, so this is why it is closed. Feel free to point to it

[ErikMaki]

"gem install resque" and "bundle update" don't grab the latest commits. Does resque need a version change for these commands to work?

[zarnautovi]

My version is 1.27.4 (last one that bundle is fetching) and I still have those warnings. When can we expect new verison that have this fix?

[zohaib-sarwar-confiz]

I am using Redis version 4.0.2 and my resque version is 1.27.4 but I am facing same issue.

[zazaian]

@rafaelfranca has no new release been issued? Why hasn't this fix been integrated into a modified release yet?

[NDuggan]

@rafaelfranca @zazaian +1 - these warnings are so noisy! Prefer to link to a released version as opposed to the master branch.

[pjrebsch]

Looks like this issue was resolved by #1606 which is now included in release 2.0.0 made available on November 6, 2018.