[00:55:59] did something happen to git? [00:56:45] UserProd: What do you mean? [00:56:49] I think Git still exists. [00:56:57] as in, i'm getting weird errors [00:57:04] like right now i'm looking at http://git.wikimedia.org/summary/mediawiki%2Fextensions%2FEcho [00:57:08] and don't see any branches [00:57:48] GitHub is probably more stable. [00:58:03] We mirror the code repos there. [00:58:10] It also has vastly better search. [00:58:48] UserProd: git doesn't want to load for me, so I doubt it's a problem at your end [00:59:03] ah ok, thanks for checking [00:59:12] Yeah, it doesn't seem to be loading here. [00:59:32] You can file a bug at https://bugzilla.wikimedia.org if you'd like. [00:59:52] kk thnx [00:59:55] But I think git.wikimedia.org is a neglected service, so other than a server restart at some point, I wouldn't expect much. [01:00:03] :) [01:00:04] poor git [01:00:10] .wikimedia.org [01:00:13] :-) [01:05:47] Gloria: is git.wikimedia down? [01:07:12] Probably. [01:07:19] Someone just mentioned this in here. [01:23:52] Gloria: seems to work now [01:23:54] cool [08:01:54] Replies welcome: https://en.wikipedia.org/wiki/User_talk:Scottywong#Cross-wiki_recent_changes_filter [08:02:22] I found his tool on toolserver rather easily, but I can't search tools.wmflabs.org [09:21:32] Hey WMF [09:21:35] http://lists.wikimedia.org/pipermail/design/2014-April/001790.html [09:21:45] Talk about canvassing on a private mailing list, eh? [09:22:25] eh "private"? [09:22:51] [Product] [09:40:45] guillom: On a related note [09:41:14] "I wasn't informed!" comments piss me off big time] [09:41:25] we announced TR twice in Tech News [09:48:08] odder: that doesn't help if people don't understand what's meant by "typography" (just to mention one thing) [09:48:50] I know; I'm just pointing out that this particular change - even if I don't like it - was announced pretty widely [11:02:12] odder: well, we'll see how many thing they were not told :) at least a few thousands knew, thanks to BetaFeatures (which I'd consider a communication tool) [11:08:59] odder: Even if it had been announced via a blinking CentralNotice banner, there would still be people who would complain that they weren't informed. [11:09:32] hell, a lot more people would complain about the blinking bit [11:15:27] CW RC is one of those perennial proposals that get stalled in development [11:16:04] has been suggested and reported as a ticket in bugzilla but the only current implementation is an IRC one for small wikis [11:20:16] guillom: blinking banners are the best way for people not to notice something [11:20:59] Withoutaname: I've not asked anything like that :) we have plenty of crosswiki RC/log tools [11:21:18] but they're usually focused on research by username rather than namespace or other things [11:22:00] interesting though [11:22:08] how would you filter the feed [11:22:21] guillom: I don't remember a single time in years that I followed centralnotice banner links; though many times I clicked the link by mistake due to those horrible dismiss icons which are almost always broken, or load too late [11:22:23] can we even do it by wiki? let alone by namespace? [11:22:41] Withoutaname: weren't you replying to my message above? I linked a tool which does that already [11:23:29] https://en.wikipedia.org/wiki/User_talk:Scottywong#Cross-wiki_recent_changes_filter [11:23:47] there is also one for id.wiki [11:23:50] that's definitely interesting [11:24:18] yes, or very depressing if it's going to die with toolserver like most of the good things [11:37:11] odder: https://www.mediawiki.org/wiki/Talk:Typography_refresh#Show_Deploy_time.2Fplan_in_the_beta_tab [11:37:14] sorry, no [11:37:23] odder: https://www.mediawiki.org/wiki/Talk:Typography_refresh#Formal_Beta_status_.28or_a_dashboard.29 [11:39:17] gry: did you see the leftovers discussion on design@ list [11:39:42] there may be some beta features spin offs: one, two, three or none [11:40:09] Nemo_bis, forks of the betafeatures extension? [11:42:04] did you just evaporate on me? [11:42:17] I didn't know I am that warm [11:43:36] spin offs, not forks [11:44:33] I didn't know we had a mirror there https://www.gitorious.org/analytics [11:44:49] you'll have to pardon me not parsing the first post (http://lists.wikimedia.org/pipermail/design/2014-April/001792.html) so I don't think I'll try reading the rest [11:45:02] so you'll have to be a bit more verbose if you want to convey the idea [12:06:02] Is there any way for non-registered users to override typography refresh? [12:07:47] They'd have to ask someone with privilege to edit MediaWiki:Vector.css [12:08:20] no other option? [12:08:38] Or set the browser's settings to ignore site CSS. [12:08:44] I saw this http://www.mediawiki.org/wiki/User:84.250.115.184/vector.css (does it work for IPs?) [12:08:59] whym_away: That really is not an option. [12:11:35] Glaisher_: I didn't know that was possible, but apparently MediaWiki does allow that when IP users are allowed to create user subpages. [12:12:22] I have confirmed on my local instance. [12:13:10] Hmm, maybe not, it was only for preview for me. [12:21:10] Glaisher_: ?useskin=monobook ? [12:21:35] Or just tell your browser to ignore font settings of websites; that does most of the trick [12:21:51] Another option is to append useskin=monobook or some other skin to the URL [12:21:51] http://en.wikipedia.org/wiki/Main%20Page?useskin=monobook [12:21:51] Well the problem is that doesn't exactly persist beyond the current page [12:22:10] sure [12:22:35] it would be trivial to make a firefox/chromium extension to give unregistered users the gift of monobook though [12:39:42] root@hume:~# Connection to hume closed by remote host. [12:39:54] hume is history:) [12:48:28] Oh. [12:50:08] log it, mutante? [12:50:18] Oh, you did in -operations [12:54:48] odder: yes:) [12:55:16] odder: you can also expect that git.wm.org doesnt die as much anymore [12:55:25] see SAL / gerrit .. laters [13:14:40] wow https://upload.wikimedia.org/wikipedia/fr/e/ed/2014-04-04_122301.jpg [13:15:40] Nemo_bis, reported already. [13:15:59] https://bugzilla.wikimedia.org/show_bug.cgi?id=63394 [14:30:21] hashar: Hi! Could you help me with a possible issue between parser tests, djvu support and jenkins job? [14:30:53] * hashar runs away screaming [14:31:01] Tpt_: what is the change # ? :-D [14:31:06] hashar: https://gerrit.wikimedia.org/r/#/c/102475/ [14:31:08] I can at least have a look at it [14:31:12] no promise though hehe [14:31:29] catching up with Wikimedia metric meeting for April 2014 ( https://www.youtube.com/watch?v=RWSwfCFpsGA ) [14:31:49] hashar: Thanks. jenkins reports a failure I can't reproduce in my local install and in a fresh lab instance [14:32:58] so LoremIpsum.djvu can't be found grr [14:33:12] hashar: yes [14:33:26] but other unit tests that relies on it works well I think [14:36:05] Tpt_: why do you need a parser test using djvu file? [14:36:25] since we already have a unit test for djbu : tests/phpunit/includes/media/DjVuTest.php [14:36:42] it already has the logic to detect whether djvu is available :-] [14:37:00] hashar: In order to have a multipage file to test the page= argument of image insertion and and tags of ProofreadPage [14:40:42] Tpt_: yeah that probably make sense :-] [14:41:26] hashar: The code the outputs tag is one big function of 500 lines and I would like to have tests before refactoring it [14:41:40] Tpt_: yeah that probably make sense :-] [14:42:03] a bunch of the logic to detect djvu works is already in DjVuTest.php, you probably want to factorize it to some new class/method [14:46:13] hashar: Ok. I'll make a new change with a DjVuSupportDetector. Should I put in in tests/ directory or in includes/media? [14:47:09] not sure :-] [14:47:51] maybe directly under /tests/ [14:48:10] or in testHelpers.inc though that one is already messy [14:49:11] hashar: It's twice 3 lines of code so a file for it may be overkill. [14:49:48] so testHelpers.inc might be good [14:50:15] you will also have to teach the parser test system about skipped tests [14:50:20] hashar: Ok. I implement it right now. [14:50:24] it only knows about success/failure ones [14:50:30] can be done in a different patch if you want [14:50:43] there is parser/ParserTestResult.php [14:50:58] hashar: Ok. Currently I tag skipped test as success. [14:52:08] another way is to pill the djvu parser tests in a different file [14:52:16] and have it loaded only when djvu is setup [14:52:31] I don't think we ever used that though. [14:52:53] the ParserFunctions extension has two .txt files [14:55:28] Tpt_: you might want to look at tests/parser/parserTest.inc which has a showTestResult() method [14:55:44] it takes a ParserTestResult as a parameter and show success/failure [14:55:59] would need to teach it skipped [14:56:05] and still return true [14:56:12] that is a bit of a mess [14:56:53] hashar: The issue is that the function will have to return a third value that is not true and not false. [14:57:39] you can just return true [14:57:54] and consider skipped tests as not failling [14:58:19] though within PHPUnit that will show as a success [14:58:28] so yeah need some refactoring to support skipped tests [15:00:51] hashar: It's what is currently done. A yellow skipped string is outputted and the runTest method returns true [15:03:00] hashar: as no more result is outputted I don't see the need of a change in ParserTestResult class. It'll just create a method showSkipped that only outputs a yellow SKIPPED and returns true [15:03:29] Tpt_: might work :] [15:06:32] hashar: Do you have any idea about why jenkins fail? [15:06:48] nna havent looked [15:07:06] apparently the new file is not uploaded when run via phpunit [15:07:36] Do you have any idea why? [15:08:08] the code in ./includes/parser/NewParserTest.php? :/ [15:08:20] yes [15:08:32] I think there are some debug log for file creation [15:08:45] and you might potentially be able to filter our parser tests being run [15:09:27] hashar: Is it possible to see these debug logs? [15:09:42] $wgDebugLogFile = '/some/place/debug.log' [15:10:31] ahh [15:10:36] there is a regex= argument [15:10:42] (in NewParserTest) [15:11:02] so you can do something like: [15:11:04] cd tests/phpunit [15:11:06] php phpunit.php --regex=Djvu includes/parser/NewParserTest.php [15:11:13] that would only run your new tests [15:11:48] we will have to rewrite the whole parser test suite one day [15:11:54] it should not rely on files existing on disk [15:12:18] we should use ./phpunit/mocks/filebackend/MockFileBackend.php and ./phpunit/mocks/filebackend/MockFSFile.php :-D [15:12:24] anyway, I need to rush out sorry :/ [15:14:42] hashar: No problem. Thanks :-) [15:36:12] siebrand: I compensated your patches and added about 1.5 millions lines of codes worth of projects to https://www.ohloh.net/orgs/wikimedia this morning :P [15:36:26] well, almost compensated; I'll try to look for more repos ;) [18:44:48] hm? https://www.ohloh.net/p/mediawiki-bugzilla [18:49:35] James_F: Any VE items for Tech News this week? [18:57:36] hey, why aren't we migrating to this :D https://www.ohloh.net/p/mediawiki-issue-tracker [19:01:01] odder: Yeah, but not much. Writing now. [19:02:28] Thanks James_F [19:40:11] Hello guys! I'm having a hard time unifying my wiki accounts. I get the error "No accounts could be confirmed using this password." when trying to merge them. Any idea of what could be the problem? [19:40:24] thedj: know this? https://www.ohloh.net/p/mediawiker [19:48:51] zlapper, what is the account name? [20:17:31] Nemo_bis: hmm, interesting. i should check if we can convert part of that into an ace plugin... [20:24:34] thedj: maybe file a bug somewhere so that we don't lose track if it's interesting [20:38:45] oh, James_F [20:39:01] ? [20:39:32] 21:01 James_F: odder: Yeah, but not much. Writing now. [20:39:42] (diff | hist) . . Tech/News/2014/15‎; 22:25:21 . . (-66)‎ . . ‎Jdforrester (WMF) (Talk | contribs)‎ (Nothing useful to discuss about VE this week.) [20:39:55] Surprising :-) [20:40:01] odder: I wrote it and decided there was nothing useful to mention, just minor bug bits. [20:40:10] Also, there's enough news from Typography refresh and Hovercards. [20:40:27] odder: Writing == https://www.mediawiki.org/wiki/VisualEditor/status#2014-04-03_.28MW_1.23wmf21.29 [20:40:31] We don't have anything from TR [20:40:37] James_F: something important happened? [20:40:53] odder: It went live yesterday. [20:41:03] odder: To all Wikipedias. [20:41:22] Yes, we informed about it in the last two issues [20:45:40] * James_F shrugs. [20:56:16] why is feedcontribution so ugly https://www.mediawiki.org/w/api.php?action=feedcontributions&user=Anomie&feedformat=atom [20:57:01] cf. https://www.mediawiki.org/w/index.php?title=Requests_for_comment/API_roadmap&feed=atom&action=history which shows actual diffs and links to the diffs [20:57:46] Nemo_bis: No idea [21:02:02] Wow. [21:02:12] “Exception caught inside exception handler.” [21:02:17] Never got that one before. [21:14:35] sjoerddebruin: lucky boy [21:14:42] :D [21:14:44] anomie|away: ok :)