Lock TTL is 2 billion seconds about redis-memolock

[OscarVanL]

I can see in one of the forks @tbrown1979 made a fix to tidy-up the lock by calling Del after publishing the result:

55184fd

But that does not address this weird TTL behaviour (suppose the caller that acquired the lock crashed, then that resource would get indefinitely locked).

[OscarVanL]

I can see this 2 billion seconds issue is confined to the GetResourceRenewable function when renew is called. I suspect it must be some glitch with the renewLockLuaScript:

    if redis.call('GET', KEYS[1]) == ARGV[1]
    then 
        redis.call('EXPIRE', KEYS[1], ARGV[2]) 
        return 1
    else 
        return 0
    end

I personally do not need the renewable lock functionality so am just going to delete it, but this serves as a warning to anyone else who was considering using this functionality, it is probably currently in a broken state.