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
What I found is not actually a bug but I got stuck with this for a while, so here it comes.
I'm expanding a marshal serialization using Redis::List with the :marshal => true flag set, and I got a weird behavior: on some of my apps the objects were loaded correctly and in others I got just the raw string from the serialization.
After some debugging, I realized that Redis::List was rescuing the failed load attempt and falling back to the string serialization: while this behavior is reasonable, it can be quite confusing to debug.
It would be nice to have Redis::Object raising a custom Exception upon failure to load the marshal serialization.
Good luck
The text was updated successfully, but these errors were encountered:
Appreciate the report. I looked into this quite a bit, and there's really no fix since redis-objects follows the recommended practice of rescue'ing marshal/dump failures with the raw data. Sorry this hit you.
Hey! Really nice and useful gem here.
What I found is not actually a bug but I got stuck with this for a while, so here it comes.
I'm expanding a marshal serialization using Redis::List with the
:marshal => true
flag set, and I got a weird behavior: on some of my apps the objects were loaded correctly and in others I got just the raw string from the serialization.After some debugging, I realized that Redis::List was rescuing the failed load attempt and falling back to the string serialization: while this behavior is reasonable, it can be quite confusing to debug.
It would be nice to have Redis::Object raising a custom Exception upon failure to load the marshal serialization.
Good luck
The text was updated successfully, but these errors were encountered: