You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Memcached interprets expirations over 30 days (so over 2592000 seconds) as UNIX timestamps (see https://code.google.com/p/memcached/wiki/NewProgramming#Expiration). That case is not handled in code, so when passing the 30 days threshold keys are immediately expired as the resulting "timestamp" is in the past.
Memcached interprets expirations over 30 days (so over 2592000 seconds) as UNIX timestamps (see https://code.google.com/p/memcached/wiki/NewProgramming#Expiration). That case is not handled in code, so when passing the 30 days threshold keys are immediately expired as the resulting "timestamp" is in the past.
I wanted to handle that by setting https://github.com/mumoshu/play2-memcached/blob/master/plugin/src/main/scala/com/github/mumoshu/play2/memcached/MemcachedPlugin.scala#L136 to
System.currentTimeMillis() + expiration
but it looks like memcached client is only handlingint
s so that would be extremely risky. Ideas?The text was updated successfully, but these errors were encountered: