Redis Fix - namespace key can grow to GB size

Describe the bug Since I migrated to keyv it looks like the amount of freeable memory is declining in constant rate: https://imgur.com/a/77kOTD7 (20 Jul is when I released changes for keyv migration).

I expect it to be related to the namespace:... key, that in my case can grow to more than 15GB in actively used cache.

To Reproduce I would expect that adding a bunch of big keys for short living values will cause the namespace:... size to constantly grow.

Expected behavior I would expect to have some auto-purging mechanism?

Tests (Bonus!!!) N/A

Additional context N/A

[KODerFunk]

I have another issue around this.redis.sadd(. I use commandTimeout option and some errors dont catch in project-code. As it turned out, these are timeouts on the sadd command. Until I figured out why my catch does not work and the error goes to unhandledRejection. I need the ability to disable this, I also have to make class MyKeyvRedis extends KeyvRedis in the project and override not only the set method, but also clear (remove smembers, add throw new MyError) and delete (remove srem).

[PhantomRay]

As a temporary workaround, I use the following code:

class MyKeyvRedis extends KeyvRedis {
  async set(key, value, ttl) {
    if (typeof value === 'undefined') {
      return Promise.resolve(undefined);
    }

    return Promise.resolve().then(() => {
      if (typeof ttl === 'number') {
        return this.redis.set(key, value, 'PX', ttl);
      }

      return this.redis.set(key, value);
    });
  }
}

As you can see, I removed this.redis.sadd(this._getNamespace(), key);