Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Version 2.13 as well as 2.x from git (release is missing, so can't select here):
Got this one:
PHP Fatal error: Cannot use object of type Predis\\Response\\Status as array in .../sites/all/modules/redis/lib/Redis/Lock/Backend/Predis.php on line 55
Comment | File | Size | Author |
---|---|---|---|
#9 | redis-2507997.patch | 533 bytes | kfritsche |
Comments
Comment #1
pounardThank you for reporting. Which Predis version are you using ?
I'll try to fix this ASAP, but I need to test with the same version as you are.
Comment #2
geek-merlinversion sais 1.0.2-dev, file timstamps 2015-01-02,
so this is current dev from https://github.com/nrk/predis
Comment #3
pounardComment #4
glass.dimly CreditAttribution: glass.dimly commentedI'm getting this too, v1.0.2 (2015-xx-xx) of Predis library, 7.x-2.15 version of this module.
Comment #5
glass.dimly CreditAttribution: glass.dimly commentedComment #6
glass.dimly CreditAttribution: glass.dimly commentedSwitching to PhpRedis as a backend is a workaround that fixed this problem for me.
Comment #7
glass.dimly CreditAttribution: glass.dimly commentedI also just pulled down the latest from the predis repo here and replicated the issue: https://github.com/nrk/predis
I replicated this issue by saving a view and I think clearing the cache also triggered this.
It appears to have quuiiite a few changes, even though the version number is unchanged. That is, the version number is the same as my comment #4 but the code is different.
Comment #8
pounardThank you very much for the time you spent into this, I hope I'll be able to proceed to some debugging myself soon.
Comment #9
kfritschePatch attached for Predis 1.0.3.
Works for us here, but didn't tested downwards compatibility with older Predis versions.
Comment #10
Drupa1ish CreditAttribution: Drupa1ish at EuroDomenii commented#9 works for me. Thanks!
Comment #11
pounardI did not forget you, I still don't get the chance to have the sufficient time to work on Redis' module maintenance, will do ASAP. This bug and associated fix needs to be run through the whole unit tests to ensure we don't forget anywhere it could fail.
Does this happen only when you are using the lock backend and not using the cache backend ?
Comment #12
Drupa1ish CreditAttribution: Drupa1ish at EuroDomenii commented@pounard Yes, it occurs only with
$conf['lock_inc'] = 'sites/all/modules/redis/redis.lock.inc';
With default drupal lock works just fine.