Cache lock refresh() for long-running operations

[justinas55]

Hello,

It would be nice to have a refresh() method on Cache lock instance, that would refresh lock TTL without releasing the lock. This would allow safe long-running operations without compromising with excessive TTL.
As an example such feature is implemented and documented in Symfony: https://symfony.com/doc/current/components/lock.html#expiring-locks .

Currently the closest workaround I found is this:

$lock = Cache::lock('test', 30);
try {
  if(!$lock->get()) {
    throw ...
  }

  $lockStart = time();

  while(!$finished) {
    if(time() - $lockStart > 15) {
       $lock->release();
       // non-atomic - another operation may acquire the lock here, and this instance then must stop/error out depending on specific case
       if(!$lock->get()) {
         throw ...
       }

       $lockStart = time();
    }

   // do actual processing
  }
} finally {
  $lock->release();
}

Having ->refresh(), same code could be simplified and made reliable:

$lock = Cache::lock('test', 30);
try {
  if(!$lock->get()) {
    throw ...
  }

  while(!$finished) {
    $lock->refresh();

   // do actual processing
  }
} finally {
  $lock->release();
}

Haven't found related issues, curious if this has been considered, is there known limitations to implementing this? Should be possible with Redis, probably utilizing transactions, but not sure about the other stores.

Thanks for checking!