Kristofer Karlsson
Kristofer Karlsson
No, I am still not sure if this change even makes sense on a high level.
Thanks for the report! I will look into it.
To clarify - what kind of error do you see? Are entries expiring too late or too early?
I could reproduce it by changing the memcached version, see: https://github.com/spotify/folsom/pull/113 It looks more like a regression in memcached itself than a problem in folsom.
Testing with more versions of memcached, it seems to depend more on type of image than version. Fails on ol-7 but works on debian / regular builds. According to specification:...
Good catch! I'll take a look at that.
The provided ttl should not be a timestamp - we could extend the API to be more explicit, like adding `.set(key, value, instant)` or `.set(key, value, duration)`
Does this change make sense to start with? Do you think it would solve your issues? https://github.com/spotify/folsom/pull/114
Partially solved in release 1.3.0.
I agree it would be useful. I tried playing around with adding something, but without having an explicit use case in mind it is harder, so I would also prefer...