Jarkko Laine

Just FYI, we have a similar issue where the lock remains intact even though there are no jobs whatsoever either queued up or processing. Haven't been able to pinpoint the...

@Aryk I don't remember exactly anymore, but I believe you know at least because you're getting the `ActiveJob::Uniqueness::JobNotUnique` exception when trying to enqueue a job with the same paeans.

@zarqman We have this same issue with 2.0.0 and 2.0.1 even though we're using redis 5.0.6. ``` redis (5.0.6) redis-client (>= 0.9.0) redlock (2.0.1) ``` The code in question (works...

> Which version of Redis (the database, not the gem) are you using, @jarkko? I saw that error, before upgrading to at least v6. 6.2.5

FWIW, bumping to 7.0.8 made no difference. I guess the issue is somehow related to the switch from Redis to RedisClient in Redlock. Our own client above (`REDIS`) is still...

One simple addition to @zarqman's notes would be to add a changelog file. It would be trivial to spot the changes from there , whereas you don't necessarily read through...