[18:02:19] <MaxSem>	 yes
[18:02:22] <^demon>	 Ok, done. Lemme know if you have any problems.
[18:08:30] <MaxSem>	 ^demon, thanks
[18:08:36] <^demon>	 you're welcome.
[18:13:09] <RoanKattouw>	 robla: Could you let me know when you guys are going live on MW.org?
[18:13:38] <robla>	 RoanKattouw: talk to Reedy
[20:04:05] <Eloquence>	 https://www.mediawiki.org/wiki/Special:RecentChanges is broken - known?
[20:05:00] <RoanKattouw>	 Whoops
[20:05:03] <RoanKattouw>	 No I didn't know that
[20:05:04] <RoanKattouw>	 Looking
[20:05:21] <RoanKattouw>	 2012-08-06 20:04:53 srv237 mediawikiwiki: [2a56f8f6] /wiki/Special:RecentChanges   Exception from line 310 of /usr/local/apache/common-local/php-1.20wmf9/includes/MagicWord.php: Error: invalid magic word 'pagesincategory_all'
[20:05:23] <RoanKattouw>	 srsly?
[20:09:35] <AaronSchulz>	 yeah, saw that in the log
[20:10:08] <RoanKattouw>	 Probably a l10n-cache-out-of-date problem, I'm syncing out the l10n cache but it's slw
[20:12:47] <Eloquence>	 VE appears to be broken as well
[20:12:53] <RoanKattouw>	 Yeah it would be
[20:12:55] <RoanKattouw>	 That's knwon
[20:13:01] <Eloquence>	 k
[20:13:06] <RoanKattouw>	 I hadn't upgraded Parsoid yet because the new Parsoid box was supposed to come up
[20:13:18] <RoanKattouw>	 But we just found out the new box doesn't have an OS yet, so that means more bureaucracy
[20:14:06] <RoanKattouw>	 Eloquence: Does VE work now?
[20:14:31] <Eloquence>	 still getting Uncaught TypeError: Cannot read property 'open' of undefined
[20:14:37] <RoanKattouw>	 Whoa
[20:14:43] <RoanKattouw>	 OK so the client side JS is broken
[20:14:45] <RoanKattouw>	 Lemme look at that
[20:17:54] <Eloquence>	 fyi, still getting sporadic errors on RC
[20:18:01] <Eloquence>	 especially with filter parameters e.g. http://www.mediawiki.org/w/index.php?namespace=&tagfilter=&translations=filter&title=Special%3ARecentChanges
[20:18:31] <RoanKattouw>	 Yeah, half the cluster has the new l10n cache now and the other half doesn't
[20:18:34] <Eloquence>	 k
[20:18:54] <RoanKattouw>	 So whether you hit a broken Apache or a fixed one depends on how much the load balancer likes you
[20:19:08] <Eloquence>	 I'm happy to say that it mostly likes me
[20:19:46] <^demon>	 Apache likes no one :(
[20:32:45] <RoanKattouw>	 OK l10n is pushed through
[20:32:47] <RoanKattouw>	 Working on the VE bug now
[20:33:17] <RoanKattouw>	 Fixed the bug Eloquence reported while loading text into VE, that was because I hadn't done the Parsoid upgrade correctly and the old and new versions were running alongside each other
[20:33:25] <RoanKattouw>	 There is still a bug /saving/ text though
[21:14:38] <RoanKattouw>	 gwicke: I found another bug. Going to http://localhost:8000//Foo:Bar results in Parsoid trying to load Foo::Bar
[21:14:45] <RoanKattouw>	 i.e. double slash results in double colon
[21:25:50] <gwicke>	 RoanKattouw: ok, is this a problem in practice?
[21:25:54] <RoanKattouw>	 Yes
[21:25:59] <RoanKattouw>	 Well, I worked around it for now
[21:26:30] <RoanKattouw>	 But $wgVisualEditorParsoidURL can be set to something like 'http://foobar:8000/' or 'http://foobar:8000' . So we just add a slash, because double slashes are supposed to be safe, right? :) (Famous last words)
[21:26:33] <gwicke>	 normally you'd have a prefix
[21:26:38] <RoanKattouw>	 Sure
[21:26:49] <RoanKattouw>	 But I could still potentially have //mw:Foo:Bar
[21:27:04] <gwicke>	 I guess you could just strip a trailing slash
[21:27:16] <gwicke>	 from $wgVisualEditorParsoidURL
[21:27:27] <RoanKattouw>	 I could
[21:27:46] <RoanKattouw>	 But I'm more likely to spend that time figuring out why it's doubling the colons
[21:27:53] <gwicke>	 easier than tweaking all the regexps to take double slashes into account
[21:28:25] <RoanKattouw>	 Well see the second slash isn't actually captured
[21:28:31] <RoanKattouw>	 It's not trying to parse [[/Foo:Bar]] or something
[21:28:36] <RoanKattouw>	 Instead, it doubles the colons
[21:29:03] <gwicke>	 fixing this on the PHP side should be a single line
[21:29:31] <RoanKattouw>	 Yeah I could do that as a workaround
[21:29:52] <RoanKattouw>	 Probably will in the short term
[21:30:30] <RoanKattouw>	 But I'll want to fix this in Parsoid too because there's no way this kind of behavior is HTTP-compliant :D
[21:30:42] <RoanKattouw>	 It could be another bug in that Node library I guess
[21:35:43] <gwicke>	 RoanKattouw: fixing that in express would definitely be easier than working around it in all those routing regexps
[21:35:51] <gwicke>	 similar for urlencoding
[21:36:01] <RoanKattouw>	 Yeah the urlencoding gets on my nerves too
[21:36:10] <RoanKattouw>	 The double colon thing is really f-ing crazy
[21:36:20] <RoanKattouw>	 Wouldn't be surprised if that was an express bug, but it would be a new low
[21:36:24] <gwicke>	 but since we won't use JS forever, spending too much time on it might not be worth it
[21:36:43] <RoanKattouw>	 True
[21:40:52] <RoanKattouw>	 Eloquence: VE is now back up
[21:41:36] <Eloquence>	 confirmed, thanks :)
[22:53:50] <^demon>	 Quick Echo question. Is there a way to dismiss a notification without actually clicking on it?
[22:53:56] <^demon>	 Maybe I'm missing something obvious.
[23:26:32] * AaronSchulz  has none :(