[17:57:50] dbrant: mdholloway: niedzielski: I've been looking at persisting EventLogging events to disk. On iOS we used CoreData. It seems like there are custom wrapper classes for SQLite in Android. I assume you'd want to use those, but I thought I'd check before I get too far in [18:06:40] amrox: hey, i'm taking a late lunch and just about to run out the door -- wanna jump on a hangout and chat about it when i get back back? [18:06:53] sure [18:07:04] amrox: ok cool, tty in a bit [19:43:16] mdholloway: I'm free for the next 2ish hours [19:43:36] amrox: ok cool. just catching up on a couple of quick things and then i'll ping you [19:43:50] mdholloway: k, take your time [19:44:08] is the patch you already submitted related (i.e., should i look at it first) or is this separate? [19:44:58] it is related, yes. The reason for centralizing calls to EventLogging is so there is a central place to store and queue them [19:45:32] I didn't push an queuing or perstitence code yet though [20:05:53] amrox: ok! ready to chat anytime [20:06:32] mdholloway: k - call you on hangouts? [20:06:41] amrox: sure [20:30:33] mdholloway: I think I did it right: https://gerrit.wikimedia.org/r/#/c/359008/ [20:31:34] amrox: yep, everything looks good as far as the revision appearing correctly! [20:32:10] amrox: only, still more rules to follow with the Bug: statement -- it has to be the last line with the exception of the Change-Id: line (i.e., no lines in between) [20:32:29] amrox: sorry, i know [20:32:57] mdholloway: hah, I was so close [20:33:15] nzr: we still on? [20:34:17] maxbinder: oops... texted you on gchat