[00:38:56] <refeed[m]>	 jdlrobson: Hi, are you around?
[00:41:21] <Volker_E>	 refeed[m]: jdlrobson is on short vacation
[00:41:45] <Volker_E>	 anyone here who knows how often http://reading-web-staging.wmflabs.org/ gets updated?
[00:41:54] <Volker_E>	 as new core/new dependencies?
[00:43:30] <refeed[m]>	 Volker_E: okay, thanks
[00:47:21] <refeed[m]>	 btw, when will jdlrobson come back from his vacation?
[00:50:07] <Volker_E>	 refeed[m]: until 21 Dec
[00:50:20] <Volker_E>	 sry, 21 he's gonna be back
[00:54:18] <refeed[m]>	 hmm okay, still a week again :( . Btw I'm currently working on gci task that he mentored (codesniff thing), should I abandon the task first? I have made two CRs in gerrit for the task
[15:32:39] <refeed[m]>	 okay, the patch has been reviewed by Legoktm
[20:02:20] <hashar>	 bmansurov: hello :)  if you are around it seems  chromium-render  tests block indefinitely :)
[20:02:31] <hashar>	 something something block at the end of the mocha run
[20:22:30] <bmansurov>	 hashar: sure, I'll take a look. meeting now ;)
[20:22:32] <bmansurov>	 thanks
[20:25:15] <hashar>	 bmansurov: I have a basic CI job setup  which you can trigger by commenting "check experimental" 
[20:25:26] <hashar>	 some example runs are on https://integration.wikimedia.org/ci/job/chromium-render-npm-browser-node-6-docker/
[20:25:38] <hashar>	 no hurry :)
[20:26:36] <bmansurov>	 hashar: cool!
[20:26:43] <hashar>	 bahh
[20:26:58] <bmansurov>	 I think we have the same problem locally, I just didn't get around to fixing the issue. 
[20:27:09] <bmansurov>	 It's a good time to capture this in a ticket.
[20:27:16] <hashar>	 yeah will fill one
[20:27:22] <bmansurov>	 I'll do so and ping you there in case you have more info to add.
[20:27:35] <hashar>	 turns out that is when I use my local chromium instead of the puppeteer one  :D
[20:27:54] <bmansurov>	 oh that's useful info
[20:27:56] <bmansurov>	 didn't know that
[20:27:57] <hashar>	 so probably we can keep using https://phabricator.wikimedia.org/T179552  "set jenkins for chromium render"
[20:28:12] <bmansurov>	 that works too
[20:28:59] <bmansurov>	 my guess is that the docker image doesn't have access to the local chromium and thus tests are failing
[21:26:36] <hashar>	 bmansurov: I don't even understand nowadays javascript :]   That looks like an entirely new language to me bah
[21:26:53] <hashar>	 bmansurov: I guess Phuedx and I will sync about it next monday! Don't worry :]
[23:17:44] <mhurd>	 Hey all! I noticed reference "[7]" on "enwiki > Nights: Journey of Dreams" looks like this on mobile web... <a href="#cite_note-FOOTNOTESega20074%E2%80%935-8">[7]</a> ...but like this on desktop... <a href="#cite_note-FOOTNOTESega20074–5-8">[7]</a>
[23:17:50] <mhurd>	 ^ is that intentional?
[23:19:58] <mhurd>	 MaxSem: ^ maybe related to the section id encoding change from a while back?
[23:20:48] <MaxSem>	 mhurd: does your content service use parsoid for pageviews?
[23:22:51] <mhurd>	 MaxSem: android does iirc, but we're still using mobileview
[23:24:55] <MaxSem>	 so, an mdash(?) not getting normalized to ol dumb -
[23:25:03] <MaxSem>	 is there a problem about it?
[23:36:08] <mhurd>	 MaxSem: just seemed odd that the link uses percent encoding... <a href="#cite_note-FOOTNOTESega20074%E2%80%935-8">[7]</a> ...but the thing it links to doesn't... <li id="cite_note-FOOTNOTESega20074–5-8">. it causes a bug with some JS we use - i can fix easily enough but thought upstream fix for consistency might be nice too
[23:40:43] <mhurd>	 MaxSem: guessing i should file a ticket against "mobile"?
[23:44:04] <MaxSem>	 waait
[23:44:12] <MaxSem>	 – is mdash
[23:44:17] <MaxSem>	 so there's no bug
[23:45:08] <MaxSem>	 these 2 representations should be handled as o ne
[23:45:13] <MaxSem>	 an browsers do
[23:48:42] <mhurd>	 MaxSem: it's just inconsistent i guess. and it did cause a bug with some reference gathering JS used by apps. would also be nice for debugging if you could, say, search for an id and see the 2 matches you expect instead of just one because the other one uses different encoding. confused me at a first when i tried to do so :)