[07:08:55] !bot [07:08:56] A bot is an automatic process which interacts with MediaWiki as though it were a human editor and is designed to simplify repetitive actions too cumbersome to do manually. An overview of how to create a bot and a list of known frameworks can be found at http://en.wikipedia.org/wiki/Wikipedia:Creating_a_bot [07:59:28] 'morning [08:00:36] I wrote a patch for yesterday's problem == one is unable to embed a bmp image through an external link ( http://www.mediawiki.org/wiki/Help:Images#Files_at_other_websites ) [08:00:42] http://www.mediawiki.org/w/index.php?title=Project:Sandbox&oldid=556030 [11:14:20] hashar: We've got company [11:14:21] http://integration.wmflabs.org/testswarm/user/browserstack [11:14:22] a living swarm! [11:14:43] http://integration.wmflabs.org/testswarm/job/2 [11:15:55] OH MY GOD!! [11:16:13] \O/ [11:16:32] will check that after lunch [11:16:33] kudos!! [11:16:35] :-) [11:17:18] Krinkle: feel free to adapt the testswarm submit job :-D [11:17:25] easy now.. [11:17:32] :D [11:17:37] we can make Jenkins send job request this afternoon :-] [11:17:49] could even send them to both the oldl and the new testswarm [11:18:06] oldl / old [11:18:36] I am out for now [11:18:58] hashar: k [11:19:09] hashar: btw, we don't need both. the old one is practically dead [11:19:14] yeah [11:19:32] lunnhchh [12:27:27] back [12:45:28] hashar: alrighty [12:45:41] currently going through some IE9 bugs that I discovered through swarm now [12:49:08] <^demon> Krinkle: I just realized the commit msg wrapping isn't needed at all as of Gerrit 2.4.x [12:49:14] <^demon> example commit on 2.4: https://gerrit-review.googlesource.com/#/c/36510/ [12:50:12] ^demon: Hm... wrapped server side? Was your commit changed? [12:50:28] <^demon> It's put in a pretty little box :) [12:50:44] still good to have them wrapped for people doing 'git log' in a terminal [12:50:51] I hate it when it wraps badly :-] [12:50:56] <^demon> Another random commit: https://gerrit-review.googlesource.com/#/c/35221/ [12:51:30] <^demon> hashar: Yeah, proper formatting is still nice for CLI users, but I'm just saying gerrit fixed the "people who write long commit messages give gerrit a horiz. scrollbar" [12:52:16] that is a good news [12:52:22] I am pretty sure nike opened a bug for it [12:52:29] (in our bug tracker I mean) [12:53:16] 57 bugs under git/gerrit component :-( [13:01:54] git is really crazy stuff [13:02:21] git log --oneline --check [13:02:22] !! [13:02:22] A red exclamation mark (!) in the recent changes or on your watchlist means that edit is not patrolled yet. Read more about patrolling at https://www.mediawiki.org/wiki/Help:Patrolled_edits and configuration at https://www.mediawiki.org/wiki/Manual:$wgUseRCPatrol [13:02:35] that would display commits introducing whitespaces [13:03:30] which mean I could add a step in jenkins to reject a commit :-] [13:56:29] hashar: watch this http://integration.wmflabs.org/testswarm/job/3 [13:56:40] I enabled all browsers according to wmf traffic stats [13:56:42] :D [13:56:59] there is a 10 browser simultan limit, so it will take a minute, but still pretty quick [13:57:08] Pfft [13:57:10] I'm on chrome 21 [13:57:54] wmf non-mobile traffic > 0.1% (minus ones not in browerstack) [13:58:10] Opera 11.1 and 11.5 are off the radar [13:58:55] I love the "work in progress" icons [13:59:07] so I guess we can drop the debian package ? ;-D [13:59:23] though we will probably want to write some puppet class [13:59:40] Krinkle: we need a video capture of the tests being worked on :-] [14:00:19] yeah, I made those spinning icons [14:00:24] css3 animation :) [14:00:31] ohhhh [14:00:36] \O/ [14:00:50] http://ganglia.wmflabs.org/latest/?r=20min&cs=&ce=&c=integration&h=integration-apache1&tab=m&vn=&mc=2&z=medium&metric_group=ALLGROUPS [14:01:07] hashar: maybe CACHE_ANYTHING? [14:01:30] I think I have set it to use apc [14:01:50] * Krinkle tries CACHE_ANYTHING - especially resource loader computation is central here [14:01:56] well, it doesn't really matter though [14:02:01] I'm gonna remove mediawiki from it soon [14:02:21] i just installed there because I need to point it to the inject.js file from that swarm [18:09:09] Thanks, kaldari, bsitu. Just want to know what gerrit commits you plan on releasing. :-) [18:09:33] all of PageTriage changes in master branch [18:10:08] plus ClickTracking update for E3 to test.wiki [18:12:06] Looks all reviewed. I thought some of it wasn't reviewed [18:13:51] I only see this: https://gerrit.wikimedia.org/r/#/c/13289/ [18:16:50] yes, the ClickTracking change is not yet reviewed [18:16:59] but we're doing that one this afternoon [18:17:32] If anyone wants to review https://gerrit.wikimedia.org/r/#/c/13289/ in the meantime, that would be awesome :) [18:17:37] kaldari: Okay, so I suppose you're already starting the deploy then. [18:18:00] yeah, we're doing PageTriage deploy to wmf6 first [18:18:09] I'll look at it and +1 it. You proceed with E2 deploy and when it's on test, tell Fabrice. [18:18:09] and then testing on test.wiki [18:18:19] will do [18:18:46] alolita: ^ [18:33:50] did someone just deploy? [18:34:02] Yeah things are fucked up. [18:34:09] indeed they are [18:34:57] Ryan_Lane: kaldari: yeah, we're doing PageTriage deploy to wmf6 first [18:35:13] where are you doing this? [18:35:32] is the bot broken? [18:35:35] I don't see logs [18:35:57] I'm not sure he's started. [18:36:02] that's hashar's change not ours [18:36:16] get on wikimedia-tech for the lags [18:36:17] logs [18:36:48] ah, so you guys didn't start yet, then? [18:38:07] The E2 deployment has only been pushed to test so far [18:38:14] i.e. wmf6, not wmf5 [18:39:04] hashar pushed out a config change a few minutes ago though [18:39:11] unrelated to our deployment [18:41:08] so I have pushed a few changes made to CommonSettings.php that were unrelated and tested on 'beta' / tested by me manually [18:41:17] somehow something is screwed out so I just reverted all the cchanges [18:41:26] sorry for the trouble with your deployment :-((( [18:42:45] hashar: are all the config issues cleaned up at this point, i.e. is it safe for us to proceed with our push to wmf5? [18:42:55] yeah totally [18:43:06] that is an unrelated change doing some magic for beta [18:43:21] I instantly reverted to the previous safe version [18:45:59] yeah. sorry. I assume that since a deploy is going on, that site issues like that are related [18:46:08] hashar: you didn't check to see if a deploy was scheduled? [18:46:10] tsk tsk :) [18:48:07] I should do that stuff during european morning [18:48:10] that is quieter :-] [18:48:21] so anyway, that postpone it to at least monday ;-] [18:52:16] about to run a scap if that's cool with everyone [18:54:45] scap started [18:55:00] exciting [18:55:33] yeap, :) [19:08:36] kaldari: scap finished? [20:11:34] is there any substantive work needed anymore for us to enable HTML5 by default, other than giving fair warning before we flip the switch? [20:12:14] <^demon|away> Nothing comes to mind offhand, but I wasn't ever deeply involved. [20:12:24] in theory i think it should just be a flip [20:12:44] <^demon> Let's give brion his shell access back and let him flip it ;-) [20:12:50] noooo :) [20:13:00] ^demon, i'm still getting moderation holds on mediawiki-commits for gerrit msgs :( [20:13:03] <^demon> You can't resist forever [20:13:23] <^demon> robla: Can we push on getting me admin access to the list so I can fix ^? [20:13:40] last time we tried, we broke a bunch of bots, and I'll bet it still does. If we give fair warning before doing it though, there shouldn't be a problem. [20:14:15] <^demon> No matter how much warning you give, there will still be broken bots. But more warning is better :) [20:14:20] ^demon: do we have an RT ticket in for that? [20:14:25] <^demon> Nope, not that I know of. [20:14:44] <^demon> Should just be a simple matter of changing the list admin password for it and sending me said password. [20:14:49] <^demon> But yeah, I can file in RT for that [20:15:03] thanks [20:15:16] ops is pretty ticket-operated :) [20:15:41] <^demon> I miss the old days when I could go "Hey brion, mind changing this for me?" "Sure, one sec" [20:15:43] <^demon> :) [20:18:08] yeah though that only scales so far :) [20:18:40] <^demon> robla: https://rt.wikimedia.org/Ticket/Display.html?id=3203 [20:19:27] <^demon> brion: We just need to webscale you [20:19:32] I was going to make a MongoDB joke, but those are pretty 2010 [20:19:37] :) [20:22:36] robla: yeah, that sounds right for html5. Give some notices. Flip the switch. Go hide for a few weeks [20:23:50] I had forgotten it was already on mediawiki.org. https://bugzilla.wikimedia.org/show_bug.cgi?id=27478 [20:24:03] <^demon> robla: Can we get these? http://www.zazzle.com/i_would_prefer_t_shirts-235689879400316433 http://www.zazzle.com/2_lgtm_tee_shirt-235862924096653439 [20:24:35] oh lord [20:25:22] <^demon> I'll probably buy the "I would prefer" one :) [20:27:33] http://wikitech.wikimedia.org/view/Software_deployments#Near-term_to_be_scheduled <-now with HTML5 [20:39:24] robla, ^demon, brion: possibly relevant to your interests: http://getbarkeep.org/ [20:40:34] purty [20:41:42] <^demon> Their workflow is post-commit though, wonder if that's configurable. [20:42:15] it is purty. [20:42:26] i didn't see if it was open source. [20:42:36] if it is, we could always bolt a pre-commit workflow onto it. [20:43:14] <^demon> Potentially. It's ruby though, which is kind of a turn-off. [20:43:34] "Barkeep is unopinionated. Use it with pre-commit or post-commit workflows, and script tools on top of it if you like. " [20:43:49] maybe we can kick money to hampton to work on it. [20:43:50] <^demon> Ah, didn't see that. [20:44:01] <^demon> I was reading https://github.com/ooyala/barkeep/wiki/Comparing-Barkeep-to-other-code-review-tools [20:45:01] <^demon> Worth installing and giving it a shot. I do like the fact that they've used Reitveld, Phabricator and Gerrit before writing this. [20:45:29] <^demon> They obviously didn't wake up one day and say "Let's write our own code review system" which is totally the wrong way to do it :) [20:45:38] you learn the best-of-breed by playing with the worst-of-breed. usually this involves playing in shit, though. [20:45:53] Let's write our own wiki. [20:46:31] heh...look how many checkmarks gerrit gets :) [20:47:06] <^demon> Naturally handles pre-commit? That what it *does* [20:47:51] yeah, Gerrit pretty much stopms the competition in that area [20:47:51] <^demon> It also has syntax-highlighted diffs, if not the prettiest :) [20:48:14] "fast, clutter free UI", maybe not so much [20:48:25] <^demon> Yeah that's kinda their biggest failing point. [20:48:30] <^demon> That and "Small hackable codebase" [20:48:31] "light on process"...*sigh* [20:48:36] <^demon> but that's improving with plugins in 2.5 :)