There were cooldownttl and cooldownttlms in StoragePolicy, it's so error-prone because they served nearly the same. For example, the init function would only assign the ttl timestamp to cooldownttl, which would end up pushing cooldownttl 0 to be.
There were cooldownttl and cooldownttlms in StoragePolicy, it's so error-prone because they served nearly the same. For example, the init function would only assign the ttl timestamp to cooldownttl, which would end up pushing cooldownttl 0 to be.