[05:29:35] <phedenskog>	 morning!
[06:58:40] <phuedx>	 hey phedenskog 
[06:58:50] <phuedx>	 just taking george to nursery then i'm online proper
[07:25:41] <phedenskog>	 hello phuedx
[08:11:41] <phuedx>	 why hello
[08:25:13] <phedenskog>	 and not morning?
[08:25:51] <phedenskog>	 lets see I had a couple of things but let me get back later. hows your schedule this week, could we team up for some Grafana? 
[08:26:55] <phuedx>	 ^ phedenskog: wrong channel i think ;)
[08:27:30] <phedenskog>	 :)
[08:32:56] <phuedx>	 phedenskog: i'm close to having a working node module for creating ifbs on the fly
[08:33:20] <phuedx>	 then i'd be happy with the change to sitespeedio/sltc
[08:34:37] <phedenskog>	 that would be super. I'm continue today to setup the pi. still wanna make the mobile webpagetest dashboard cleaner, I'm having a hard time seeing things there.
[08:38:43] <phuedx>	 bmansuro_: be sure to submit a change with your refactorings
[08:38:52] <phuedx>	 because they were good and i'd be happy to merge 'em
[08:43:49] <bmansuro_>	 phuedx: cool, i'll do so later today
[09:35:24] <joakino>	 morning
[09:59:34] <phuedx>	 joakino: you call this morning?
[09:59:35] <phuedx>	 ;)
[10:00:01] <joakino>	 considering i have lunch at 3pm, yes :P
[10:13:58] <phuedx>	 pretty sure morning is defined by a time rather than an event ;P
[10:14:00] <phuedx>	 w/e
[10:42:22] <phuedx>	 phedenskog: https://openstf.io/
[10:42:34] <phuedx>	 /cc joakino
[10:42:39] <phuedx>	 just caught my eye
[10:47:47] <phedenskog>	 cool, I've starred it before but forgot about it :/
[10:50:41] <phedenskog>	 would be cool to test it
[16:01:24] <maxbinder>	 phuedx: joakino bmansuro_ retro
[17:16:47] <jhobs>	 nzr: just a heads-up, I pinged you in a declined task, but it still needs your brief attention
[17:18:22] <joakino>	 i did too ^ hehe
[17:19:42] <FlorianSW>	 dbrant: could you please take a look at https://ticket.wikimedia.org/otrs/index.pl?Action=AgentTicketZoom;TicketID=9195497 ? I'm not sure, if this is a device problem :/
[17:20:40] <dbrant>	 FlorianSW: it says I don't have access to the ticket
[17:21:30] <FlorianSW>	 o.O
[17:21:43] <FlorianSW>	 ah, wait, it's in the tech-issues queue, I'll move it
[17:22:00] <FlorianSW>	 can you try again please?
[17:22:03] <FlorianSW>	 dbrant: ^
[17:24:37] <dbrant>	 FlorianSW: ah, actually that user has resolved his own problem (in a separate thread he started in the android queue). this one can be closed.
[17:25:49] <dbrant>	 FlorianSW: https://ticket.wikimedia.org/otrs/index.pl?Action=AgentTicketZoom;TicketID=9198892
[17:28:25] <FlorianSW>	 dbrant: aha, ok, and I thought he meant mobile-l :P
[17:28:34] <FlorianSW>	 thanks for pointing me to the ticket :)
[17:29:25] <dbrant>	 np
[18:08:33] <bearND>	 mhurd I noticed on https://gerrit.wikimedia.org/r/#/c/292588/ you're asking for the revid to be included in the featured article feed response. How do you plan to use it?
[18:25:07] <mhurd>	 bearND: iirc we use it to see if we have the latest version already 
[18:25:34] <bearND>	 mhurd: so you're storing it client side, right?
[18:27:20] <bearND>	 mhurd: to see if you have the latest version you'd need to request the payload again and compare. I think using the etag would be better. Then the client networking library can do conditional requests. The one we use in Android does that automatically.
[18:27:51] <bearND>	 as long as the server provides one. MW API does provide etags, but the new RESTBase endpoints do.
[18:40:55] <bearND>	 sorry meant to write MW API doesn
[18:41:00] <bearND>	 't
[19:04:28] <niedzielski>	 mdholloway:  p/ hello! would you mind if i changed the date format used in most-read responses? it's currently like "2016/06/07" but this can't be consumed without a custom Gson date adapter in our codebase. i would like to change it to be like "2016-06-07Z".
[19:04:38] <niedzielski>	 mdholloway: i have the custom adapter built but it's a little clunky. i figure other clients of the service will probably want iso8601. the only downside would be that the date and would no longer be a string subset of the URL
[19:05:02] <mhurd>	 bearND: ya etag would be much better! can u make sure all the service bits return etags?
[19:05:09] <mdholloway>	 niedzielski: sure, i don't have a strong preference on the format of the date string
[19:05:30] <niedzielski>	 mdholloway: sweet! that should simplify the implementation a little. thanks :)
[19:07:02] <mdholloway>	 niedzielski: mhurd: i actually didn't really intend for it to be doing any work, if anything more for debugging since in the aggregated response the most-read results will be from the previous day whereas the result will be current
[19:07:14] <mdholloway>	 s/result/rest
[19:22:40] <mhurd>	 niedzielski: mdholloway: i'm not familiar with that date format - is that an android specific thing? if so i don't think the payload should be formatted making an assumption about the type of client...
[19:23:05] <bearND>	 mhurd: yes, all the MCS endpoints return etags. BTW, are you still planning on finishing the random endpoint? Or would you like me to take it?
[19:24:08] <niedzielski>	 mhurd mdholloway: not an android thing. i believe it's the default MW and javascript time format.
[19:25:03] <mhurd>	 niedzielski: ah ok
[19:26:28] <mhurd>	 bearND: oh if u can take it over that would be great! wanna chat this afternoon or tomorrow a bit? (gonna grab lunch atm)
[19:26:51] <bearND>	 mhurd: sounds good
[21:31:05] <dr0ptp4kt>	 mhurd: there in 90 secs