> > I had a good weekend, I hope you had a good one too. Yeah, I had a good weekend as well - Thanks.
> > I've pushed the "defensive mget": > > https://github.com/jmettraux/ruote-redis/commit/0e01a2e585e554e734f35... > > I hope it helps. Thanks for that. We gonna stick with our solution (with the logging) for now - just in case we need the additional info: https://github.com/tricycle/ruote-redis/tree/logging > > For the initial issue you reported, if it reappears, I wonder how we could > harden ruote-redis to deal with that. The symptom is an empty participant > list, the redis "get" returned nil. Yeah, about the initial issue... since we rolled back to ruote (and ruote-redis 2.2.0) this issue never came up again - so there is definitely a bug somewhere in the new code... unfortunately we can't really upgrade (and test) again, because this caused us serious issues with our live app. But as you can see from our ruote-redis branch (https://github.com/tricycle/ruote-redis/tree/logging), we cherry picked almost everything, except basically this commit: https://github.com/jmettraux/ruote-redis/commit/a73a1b9bb9847805dafc2da0eaa30cf6ebe8035c And I don't think that commit messes with the participant list !?! So it could be an issue with ruote itself... Unfortunately, but I wasn't able to find a commit that could've introduced an issue - mainly because there are heaps (good work on the updates btw) ! Cheers, Tom -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
