[01:50:04] Coren: you're whitelisted in CI now! :) [09:40:44] Anyone know what's going on here? https://hr.wikipedia.org/wiki/MediaWiki:Gadget-popups.js — I'm getting 'Exception encountered, of type "Exception" ' [10:23:01] Srdjan_m: Known issue [10:23:22] Reedy I'm guessing it's with the math tag [10:23:28] Yup, that's the one [11:41:21] legoktm: Danke. :-) [11:49:45] Hm. Horizon still dislikes me. Who's around I could make admin of a project to fiddle the security rules for me? [14:00:48] 503 at https://commons.wikimedia.org/wiki/Category:Beata_Vergine_della_Cintura_(Castiglione_dei_Pepoli)_-Interior [14:00:58] or anywhere actually [14:02:46] and up again [14:43:27] Hm. I'm switching my code to use ConfigFactory, so my defaults are moving to extension.json -- is there a way to have a config value there default to a namespace ID without having to put the actual number? I.e.: use NS_TEMPLATE rather than 10? [14:45:23] Coren: Not in the JSON, you can do it with a hook though [14:46:11] Hm. Might be reasonable to just use 10 since that's the only namespace in the default? [14:46:23] Coren: onRegistration [14:46:27] https://gerrit.wikimedia.org/r/#/c/279723/ is a vague example [14:46:33] * Coren checks that out. [14:47:23] Well, that does defines, not config.... But should be good to do config [15:05:14] TemplateStyles in action: http://ts.wmflabs.org/w/index.php/Template:Boilerplate [15:05:47] With the main page being an example transclusion. [15:21:13] brion: ^^ this may be of particular interest to you. [15:47:19] Volker_E: hmm, whoops, it seems i forgot about the frontend meeting today D: sorry [16:08:38] MatmaRex: Happens to the best of us, saw your review strike ;) [16:10:57] MatmaRex: (instead) [17:07:42] Is there someone who can edit this https://hr.wikipedia.org/w/index.php?title=MediaWiki:Gadget-popups.js&action=edit ? Asked a local admin to do it, but he said he couldn't because he had an error message pop up. [17:10:52] I can edit it Srdjan_m [17:11:25] Krenair: Can you change the

tag on line 1421 to "math tags" in plain text?
[17:12:43] why? it's a comment
[17:13:54] because it fixes the error "Exception encountered, of type "Exception" "
[17:14:16] "An error has occured."
[17:14:22] it did so on en.wiki anyway https://en.wikipedia.org/w/index.php?title=MediaWiki:Gadget-popups.js&diff=709402077&oldid=706293080
[17:19:22] Srdjan_m, done
[17:19:34] Krenair: awesome. thanks.
[18:00:09] Anybody know what this error means when attempting to upload an img? http://puu.sh/ogVW1/f226fc20a3.png
[18:06:53] BrownFig21: hmm. looks like a temporary issue with your internet connection
[18:07:24] try again, i guess
[19:10:43] Hm.  I'm writing unit tests, and I need fairly long strings to feed the parser.  Our style guide isn't really clear on whether I should use very long strings or here documents?
[19:12:25] Usually using long strings, ignoring code style comments
[19:14:08] i like heredoc personally
[19:14:21] but that means nothing for the style guide 
[19:23:48] Coren: you could also just put the test cases in separate files.
[19:32:29] MatmaRex: Heh, the unit testing manual on mw.o sez not to touch the filesystem.  :-)
[19:32:38] well, 'should'
[19:32:49] So I'm debating which is least worst.
[19:33:06] eh? not *write* to filesystem, i assume?
[19:33:18] we have tons of tests that *read* files.
[19:33:40] I suppose that's why "should" and not "must".  :-P
[19:33:46] e.g. all the media handling tests in core, and just about the whole abusefilter test suite
[19:34:12] It'd work just as fine with here docs.  Having dozens of 4-6 line files sounds like a poor solution.
[19:35:58] Style guide sez "Heredoc-style strings are sometimes useful", that looks like one of those times.
[19:37:30] $coren = <<< YEA
[19:40:32] * Coren patiently waits for the rest of the string... :-)
[19:40:49] sounds good
[19:40:51] YEA;
[19:42:57] Lol
[19:47:13] hahahaha
[19:47:35] nerd jokes
[19:47:38] it's all in the timing
[22:28:21] Well, I can't think of an input string that manages to generate something evil.  It's easy enough to make a hash of the resulting CSS so that it becomes useless, but I haven't found a way to make it harmful.
[22:54:02] It's either a good thing about my code or a bad thing about my imagination.
[23:02:07] i'm going to consider that a challenge. ;)
[23:03:22] MatmaRex maybe you can creat a buffer overflow exploit
[23:03:27] e
[23:18:59] MatmaRex: If I were you, I'd wait until I commit my current code first.  :-)