he is currently in san francisco, he was on irc a few hours ago.
ruaok
I got that much, ya.
he'll soon realize that he needs a ride to the south bay. :)
ocharles: take bart to SFO and be at SFO at… 1800
that should work out ok.
warp
well, he can always take the bus
;)
ruaok
you mean three buses. :)
RootWyrm_
Does BART even run that late?
ruaok
or 5
warp
ruaok: it was three for me last year, yes
ruaok
at 6pm?
yes.
from SFO to sunnyvale.
RootWyrm_
Oh 1800 gods, I'm tired.
ruaok
I guess he can bart to milbrae and catch a bus from here
RootWyrm_
OOW10 I got caught out because I was a train and a bus away from my hotel.
"It's only freaking 1AM and the trains stopped?!"
ruaok
k bed time for me.
warp
ianmcorvidae: alright, shall we look at that edit stuff before I go all around the city preparing for imminent travel?
ruaok
nn
warp
goodnight ruaok
ianmcorvidae
warp: yes, lets, if you have a bit of time
warp
ianmcorvidae: have you looked at the code and/or the output?
ianmcorvidae
I've looked at the code, not yet the output
ijabz joined the channel
I'm wondering what cross-checking you've done -- how closely have you compared the sets it produces with known problem sets (e.g. what modbot complains about)?
it looks largely obvious and I think we can probably go forward with it, but just for basic checking :)
ianmcorvidae runs a copy of it to see what I get
warp
the query only grabs edits which have a comment":null in the data field, so that should only grab edits which are actually affected.
RootWyrm_
ianmcorvidae: BTW, I forgot to thank you. That agg exposed a bug I missed.
warp
we have a comment field on many entities, but as far as I can tell the edits are all either $editdata->{comment} or $editdata->{new}->{comment}.
warp double checks that.
ianmcorvidae
RootWyrm_: hah; well, glad to be of assistance :P
warp: I was just checking that we always double-quote "comment" and that null never has a space before it, looks like we're good on that count though
RootWyrm_
ianmcorvidae: heh, I don't know if I'd go -that- far.. I don't know that I can FIX the bug. ;(
ianmcorvidae
heh
warp
ianmcorvidae: ah, yes, I assumed encode_json() to be consistent there.
or atleast has been for the past X weeks, because we're only looking at open edits.
ianmcorvidae
yeah, I think we're fine, I just wanted to double-check
warp nods.
you're happy re: data->comment and data->new->comment being the only targets?
warp
it touches 3523 edits on my local dev machine.
ianmcorvidae
3798 here
warp
ianmcorvidae: yes, I checked all the edit types with comment in them ( git grep comment | sed 's/:.*//' | sort | uniq | xargs )