[00:34:31] is there any system in what repositories are pinned on https://github.com/wikimedia ? [00:34:57] varnishkafka or puppet does not seem too interesting to the average visitor [00:38:55] There's a "Customise pinned respositories" link [00:38:57] * Reedy presses [00:39:36] I removed varnishkafka [01:08:42] If we went purely by github stars, the ios app is the winner and VE and restbase are *way* down the list. [01:18:45] bd808: Sniff. [01:19:13] I didn't boot you out :) [01:19:26] I did add the android app to fill the empty hole though [01:19:35] * James_F nods. [01:20:13] For variety of languages we should kill one of the JS (VE/RB) and add in something else in a non-PHP/Java/Python/JS/Puppet – maybe the iOS app in Obj.C isn't a bad idea. [01:20:33] * James_F kills VE. [01:21:05] iOS having a lot of stars is actually pretty awesome. They moved to using github as the primary repo with the argument that it would be easier to get contributors there. [01:21:25] I haven't checked their PRs but at least they are getting star attention [01:21:38] Yeah. [01:22:10] Also my impression is that there aren't as many FLOSS iOS apps, so it's probably an interesting member of the community. [01:22:34] there are a decent number of libraries, but yeah not many full apps [01:23:19] Especially as the iOS team does early-access stuff with Apple on new features sometimes. [01:30:47] oh sexy -- https://github.com/wikimedia/wikipedia-ios/pull/1176 -- 2fa for the ios app [01:32:21] Nice. I knew they were going to work on it "soon". [01:32:35] Next step of course is enforcing 2FA. ;-) [01:33:25] I think 2fa is a pain in the ass for 99.99% of our register users [01:33:55] I have it everywhere, but I'm a geek and have some elevated rights [01:33:55] Oh, indeed. But for anyone with RevDel/CU/RightsManagement rights… [01:34:03] *nod* [01:34:10] CU for sure [01:34:27] At last count I think I have 15 different entries in my Authenticator app. [01:34:51] mine just keeps scrolling. not sure how many in there :/ [01:35:01] I know its a pain to find some of them in the list [01:36:23] tgr, Reedy: thoughts on T157342? Would it be crazy to point to loginwiki for an OAuth handshake? [01:36:24] T157342: Users blocked from account creation on meta can not use Quarry - https://phabricator.wikimedia.org/T157342 [01:37:25] part of me wants to say that if you are blocked on meta there is maybe a reason, but if its not a global ban then not sure why we would lock folks out of a tool like Quarry [01:37:56] blocked users can still do an OAuth handshake [01:38:32] hmmm... that doesn't match what Reguyla is saying. [01:38:45] Oh would the ident api call fail? [01:39:03] I don't think anything would fail [01:39:08] I guess I should make a blocked user and test things out [01:39:25] we even have a bug report with people complaining about how blocked users can still identif [01:39:47] huh [01:41:54] bd808: we should avoid pointing people at loginwiki at all costs IMO [01:44:16] bd808: T156803 [01:44:16] T156803: Take local bans into consideration in Oauth - https://phabricator.wikimedia.org/T156803 [01:44:22] anybody a meta admin? https://meta.wikimedia.org/wiki/Special:Block/Bd808BlockedTestAccount [01:45:07] blocked [01:45:23] thx. I'll test quarry with it [01:46:58] "Your account is not allowed to use Connected Apps, contact your site administrator to find out why." [01:47:07] "Insufficient OAuth user rights, E007" [01:48:06] ugh that error messge is horrible [01:48:17] all of them are honestly [01:48:48] developers developers developers developers developers [01:49:25] huh, apparently we do that on authorize, just not on identify [01:50:11] I didn't want to say you were wrong without a test, but I actually counted on that in Striker's account creation flow. [01:50:30] So I was pretty sure that the block held [01:51:23] we have a pretty random mix of checking $user->isLocked() || $wgBlockDisablesLogin && $user->isBlocked() vs. just checking $user->isBlocked [01:51:52] IMO we should standardize on the first [01:53:15] /identify will tell you whether the user is blocked, if you care about it [01:54:37] want to file a task about it? less ugly approach than sending people to loginwiki, IMO [01:54:55] meta has customized some of the error messages, has a contact us page etc [01:55:21] allows account creation [01:56:02] on second thought I'll just repurpose T156803 [01:56:03] T156803: Take local bans into consideration in Oauth - https://phabricator.wikimedia.org/T156803 [01:57:48] * bd808 managed to lock up his laptop with too many FF tabs/windows [07:13:23] bd808: congrats on the new team! [07:13:35] how does it feel to be a manager again? :) [16:25:00] tgr: I'm not a manger until April, so I'm enjoying the last bits of my 'year of not being a manager' ;) [16:25:22] although I'm doing a lot of manager stuff for annual planning at the moment [16:38:36] bd808: time to rename #wikimedia-labs to #wikimedia-cloud ? :} [16:39:05] hashar: not yet, but soon [16:39:16] freenode supports redirecting channels [16:39:20] if it can help [16:39:35] I'm going to work up a page on potential renames and get community input on it [16:39:56] the team isn't 'official' until 2017-04-01 [16:40:11] so we have some time to work out details [16:42:31] bd808: BTW, "WMCS" is a not-quite naming conflict with Czechoslovakia (which doesn't exist any more, but makes me double-take each time). WiKloud is unique and almost as short. ;-) [16:43:15] https://people.wikimedia.org/~gwicke/bikeshed.svg [16:44:02] how does one pronounce 'WiKloud' ? [16:44:18] we-cloud? wik-loud? [16:44:54] * bd808 prefers "Cloud" and lets legoktm[NE] read that as "my butt" [16:46:03] Under WMCS I want to rename the products too and hope those see more actual use than the umbrella team name. [16:46:37] Wikimedia Labs (our OpenStack install) -> Wikimedia VPS [16:46:56] Wikimedia Tool Labs -> ?? not sure, but one idea is Tools Forge [16:47:02] or just Tools [16:47:40] Dropping the word 'tool' seems difficult since we've been using that term since 2005 or so [16:48:49] tgr|away: psysh maintainer replied to your issue just a minute ago :-} https://github.com/bobthecow/psysh/issues/353 [16:49:29] bd808: MWCGA Make Wikimedia Cloud Great Again [16:49:43] too soon hashar, too soon [16:50:11] now Freedom Cloud... ;) [16:50:49] ref: http://content.time.com/time/specials/packages/article/0,28804,2061530_2061531_2061545,00.html [16:51:18] heh. that idiocy even has an enwiki page -- https://en.wikipedia.org/wiki/Freedom_fries [16:52:19] WMFS [16:52:53] * bd808 smiles at his new team being in the left-over channel for his first WMF team [16:53:32] freedom as a service. we have no idea what that means, but how could anyone be against freedom? [16:57:29] bd808: Wik-Loud. Because you are. ;-) [17:08:55] bd808: Not just your new team, others idle there too :p [17:09:11] RainbowSprinkles: but you are my old team :) [17:09:45] Oh, I guess it wasn't exclusive "my team is in foo" [17:09:50] (and nobody else) [17:10:39] * bd808 misses the 'refugees from the Great Reorg of 2015™' topic [17:14:27] I'm still waiting for that reorg to be great again [17:14:32] And by again, I mean for the first time ever :p [18:31:33] bd808: I propose "Toolserver" [18:31:55] legoktm[NE]: heh. cause that won't cause any confusion [18:32:03] serveroftools [19:46:27] Who would you say is responsible for PdfHandler? [20:03:32] RainbowSprinkles: seems to be us, per https://www.mediawiki.org/wiki/Reading/Component_responsibility [20:49:45] tgr: goood morning! [20:50:14] I had a pleasant surprise today. I have read your Psy issue on https://github.com/bobthecow/psysh/issues/353 [20:50:36] eventualyl went to read a few other things and when I came back to the tab, magically Psysh author had written everything that was needed [20:51:06] most probably for his breakfast hehe [20:51:30] anyway I incorporated his code and rename the script to maintenance/shell.php https://gerrit.wikimedia.org/r/#/c/334217/ and it looks all fine [20:51:38] thanks a ton Gergo :) [20:52:07] tgr: Great! Sooo, there's been a spike in errors recently that all have had to do with pdf files. [20:52:08] Such as.... [20:52:28] Syntax Error: Top-level pages object is wrong type (null) [20:52:30] Syntax Error: Invalid XRef entry [20:53:18] I dunno if they're related to some bogus PDFs people have been uploading or what.... [20:54:30] (Where recently = last 2 weeks or so) [20:56:24] RainbowSprinkles: oh tyler and I talked about those yesterday [20:56:50] most definitely it is just wfShellExec() stderr that ends up in the 'hhvm' log bucket [20:57:26] and in the few cases I have investigated last week for easytimeline and others, that was always some fault in the timeline definition / pdf file / svg file etc [21:02:10] I don't think that's the case with the PDF ones. [21:02:18] I think it's bogus input for some of them [21:02:25] For timeline and svgs, yes more likely [21:02:30] DjVU has been wonky too [21:12:17] I am off to bed *wave* [23:19:42] RainbowSprinkles: is there a task? [23:19:49] I...don't think so [23:28:00] I'll file one [23:40:46] RainbowSprinkles: can you figure out whom to assign T157636 to? it's related to the usergroup expiry thing, and it breaks the browser tests [23:40:47] T157636: Global account manager (Special:CentralAuth) errors out on beta - https://phabricator.wikimedia.org/T157636