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
Right now, you can only look up cached values that have IMMORTAL_LIFETIME if the SimpleCache object has had its lifetime set explicitly to IMMORTAL_LIFETIME. This is dumb and stupid. Setting the cache object lifetime should affect the default lifetime of newly cached data, but the the expiration dates of currently cached data should be all that limits getCache() responses -- and data with perfectly good immortal lifetimes should be found!
N.B. that it is possible that changing this logic will necessitate dramatic version number increases. Think carefully!
The text was updated successfully, but these errors were encountered:
I'm inclinded to think that [the logic is borked](battis/simplecache#3) for this, but now it's working. Also, we now have a read me file. And Scrutinizer is watching us!
Right now, you can only look up cached values that have
IMMORTAL_LIFETIME
if the SimpleCache object has had its lifetime set explicitly toIMMORTAL_LIFETIME
. This is dumb and stupid. Setting the cache object lifetime should affect the default lifetime of newly cached data, but the the expiration dates of currently cached data should be all that limitsgetCache()
responses -- and data with perfectly good immortal lifetimes should be found!N.B. that it is possible that changing this logic will necessitate dramatic version number increases. Think carefully!
The text was updated successfully, but these errors were encountered: