could also be just a triggered notice/error, though...
but silently doing nothing is a little bit problematic. especially when using it for sessions you only realize it when not being able to login.
assert that the cache does not silently fail
I think this is pretty reasonable. I have some worries that it will cause exceptions where there used to be none, but all of the new exceptions are covering failures cases that probably shouldn't have been quiet in the past.
I've run into this a couple times, makes sense to add it and seems safe enough for me. People should be informed when the app is not going to cache
This is just missing a test case :(
I will add that then.
add test case