[13:45:04] gregdek, can you ping me when you're around please? [13:59:49] guillom: pong [14:46:50] hexmode: so when are you free for our Monday call? [15:00:24] sumanah: now? [15:00:38] ok, let me set up phone stuff, hexmode [15:01:40] raaawwwrr [15:01:49] 1.17 has jQuery 1.4.2 which does not have .prop() [15:02:07] hexmode: go ahead & SIP call me [15:34:22] hexmode: https://bugzilla.wikimedia.org/show_bug.cgi?id=24507 [15:37:43] lol @ bz quip: Duesentrieb: WORKSFORME GOODFORYOU [15:42:27] :) [15:42:31] how goes hexmode / sumanah ? [15:42:44] I'm all right, werdna, and you? [15:44:05] werdna: doing great! [15:44:47] werdna: what's the story on LQT atm? /me has lost track [17:15:18] I'm getting a javascript error on a line that I don't find in svn :S [17:15:54] any idea where 'return this.trigger("setData" + parts[1] + "!", [parts[0], value]).each(function() { [17:15:56] comes from? [17:16:06] What's the URL? [17:16:27] Error: this.trigger is not a function http://bits.wikimedia.org/commons.wikimedia.org/load.php?debug=true&lang=es&modules=jquery%7Cmediawiki&only=scripts&skin=monobook&version=20110926T165820Z Line: 1104 [17:17:07] That's probably in jQuery the [17:17:13] Version 1.4 that is [17:18:02] oh, right [17:18:08] it is there in REL1_17 [17:18:15] I was looking in REL1_18 [17:18:27] but why would it suddenly start failing? [17:18:28] Probably means bad data from the caller, though [17:18:39] Do you have a stack trace on that error? [17:19:29] nope [17:19:59] I have firebug disabled [17:21:56] Oh, thank you for that bug report [17:21:58] It's probably my recent merge [17:22:53] :) [17:22:59] Ooooh [17:23:01] I see [17:23:03] *RoanKattouw is an idiot [17:23:26] not such an idiot if you figured out [17:30:10] RoanKattouw: Any idea about the error reported in r97367 CR ? I don't see it locally, appears to be fine on WMF [17:30:20] !r 97367 [17:30:20] --elephant-- http://www.mediawiki.org/wiki/Special:Code/MediaWiki/97367 [17:30:50] Krinkle: I understand why it happens but haven't had time to do any RL2 work lately [17:30:52] MoodBar, MoodBar, MoodBar [17:31:04] it's RL 1 for 1.18 deployment [17:31:10] Gadgest 1* [17:31:13] Oh [17:31:36] You marked it OK and MFT'ed [17:31:39] how do I bug a developer to upload a > 100 MiB file to Commons? [17:31:40] To reproduce locally, try logging out [17:31:45] odder: File a bug and assign to me [17:31:57] RoanKattouw, wow, thanks [17:32:26] RoanKattouw, ok, another question, what is the maximum filesize? [17:32:46] There isn't any, really [17:32:47] I'll have plenty of video recordings from the 10th birthday of Polish Wikipedia conference to upload in a week or two [17:33:02] There is a page with guidelines for this somewhere on Commons [17:33:17] ok, I will look for it, thanks... [17:52:55] odder, create a bug in bugzilla, assign it to Roan, add a text attachment to the bug containing the content of the file description page in wikitext (information template, license, etc.), add a comment on the bug to say whose account should be used for the upload, and provide a link to a publicly accessible version of the file somewhere (e.g. your server) [17:53:18] That's pretty much the process; if there's no page describing it yet, you can reuse the text above to create one :) [17:53:18] Thank you for summarizing my policy so succinctly, guillom :) [17:53:26] There is a page somewhere [17:53:44] https://secure.wikimedia.org/wikipedia/commons/wiki/Help:Server-side_upload [17:54:15] *apergos growls slightly at "secure" [17:56:18] Oh, right [17:56:24] Commons has https:// now [17:56:38] :-) [18:00:55] robla: I'll have to skip the meeting, my phone is broken [18:01:31] hexmode: Reedy: binasher: joining us? [18:01:51] sec [18:02:12] sure [18:07:42] Hey, with the whole 1.18 thing, is test.wikipedia.org not pointing to fenari:/home/w/c/p [18:07:44] ? [18:07:59] It is [18:08:21] tfinc: bug #30772 ?? [18:08:34] I noticed live hacking on test seemed not to work all the time [18:08:45] and #31148 [18:08:47] RoanKattouw -- ok, confusion: see http://test.wikipedia.org/wiki/Special:UploadWizard with console open -- it complains about nonexistent resource mediawiki.Uri, which does exist. [18:08:57] Hm [18:08:59] hexmode: yeah. we saw it. [18:09:08] Try ssh'ing into srv193 and running sync-common, see if that fixes it [18:09:14] i haven't been able to reproduce it yet. [18:09:15] And hard refresh [18:09:20] but we'll take a look [18:09:26] tfinc: k [18:10:57] http://www.mediawiki.org/wiki/Special:Code/MediaWiki/tag/1.18wmf1 [18:11:00] 17 revs tagged [18:11:08] I'm working on that [18:11:21] Reedy: I'm merging 8 now [18:11:29] ah :) [18:12:15] neilk_: I am about to commit a merge that merges https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/97650 to 1.18wmf1/extensions/UploadWizard (among other things to other places), is that OK? [18:12:40] RoanKattouw: oh sure, thanks, was going to do that anyway [18:12:43] tfinc: I'm confused: are they seeing this on the *new* site? [18:12:48] OK [18:12:59] hexmode: yes. thats what their bug report says [18:15:20] hexmode: can you get them to join the mobile channel [18:15:25] we need some exact use cases [18:20:47] Hey, does anyone know how to access the database that is being accessed on test.wikipedia.org ? [18:21:02] sql testwiki [18:24:37] tfinc: I'll try [18:25:06] thanks hexmode [18:31:43] RoanKattouw: ok, trying to deploy here, mysterious errors from Resource Loader. Trevor suggests I check the apache log, but I can't read that without sudo access [18:31:51] You should be able to [18:31:57] assuming that the right log is /var/log/apache2/error.log [18:31:59] fenari:/home/wikipedia/syslog/apache.log [18:32:07] Or just run 'fatalmonitor' [18:35:40] RoanKattouw: thanks... unfortunately I see nothing relevant [18:35:52] What's your errors? [18:36:07] load.php:139 Uncaught Error: Unknown dependency: mediawiki.Uri [18:36:17] Hm [18:36:19] and a few other JS errors after that, but I'm assuming that's the main one. [18:36:45] the file is there, the resource is there. I don't know how to read the module_deps table properly, maybe something is cached there. [18:36:58] Where is the resource? [18:37:01] I don't see it in 1.18wmf1 [18:37:25] ok, I asked before if test.wikipedia.org was still pointing to 1.17wmf1, and you said yes [18:37:35] is that not the case? [18:37:44] Oh, I'm sorry [18:37:52] I remember now, someone switched it to 1.18 [18:37:56] I don't understand why [18:38:02] probably to test deploy [18:38:04] Or, well, actually, I kind of do [18:38:06] okay, this makes sense [18:38:51] BTW, are we in some world now where we have to be careful with deploy? I won't blow away the wikis which are on 1.18 if I do a normal scap? [18:39:50] No, it's fine [18:40:09] RoanKattouw: Reedy: tag sematics scrum! [18:40:33] Eh? [18:40:41] tag 1.18 means "This needs to be part of the 1.18 deploy we're currently doing" [18:40:52] No [18:40:58] 1.18 = needs to be merged to REL1_!8 [18:41:08] RoanKattouw: robla wants consistent usage of tags, so we need to document that now [18:41:20] 'cause we're not being consistent [18:41:54] RoanKattouw: then "1.18wmf1" is the wmf branch ... stuff that is actually deployed? [18:42:21] Yes [18:42:28] Tags map to branches, basically [18:42:58] right...ok, I guess I'd lost track of the fact that we waited until the last minute to branch [18:42:59] k, that isn't how I was using them [18:43:25] post118 can basically go back to 1.18 then? [18:43:52] I guess [18:44:02] Unless it needs to go to deployment too [18:44:16] basically, the absence of "1.18wmf1" means "post1.18" [18:44:55] ok... robla: clear? any place you want me to write this up? [18:46:50] hexmode: can you draft up an email to wikitech-l, maybe in Etherpad, and let's review it here before you hit send [18:46:58] sure [18:47:11] RoanKattouw: I just chatted with RobLa and Aaron -- given that I don't have very exciting changes to push this week we'll just wait until 1.18 is the standard on Commons, or until we really need to push. Thanks for your help though. [18:47:27] OK [18:47:37] That rev was in the 1.18wmf1 queue, that's why I asked [18:48:59] so...I'll stop worrying about the stuff that's marked "1.18" and only worry about the stuff marked "1.18wmf1". However, that's still a lot of stuff [18:49:21] I just merged 8 of them, refresh [18:49:25] ....and probably some superfluous stuff that we really shouldn't be futzing with [18:49:27] (The ones that were marked OK) [18:51:08] hexmode: there's two possible meanings for a revision only tagged as "1.18": [18:51:21] ? [18:51:21] 1. this revision is only important to the tarball [18:51:44] 2. this revision can wait until the dust settles before being merged to 1.18wmf1 [18:52:31] we don't really have a way of keeping track of revs that fall into the second category [18:53:40] post118deploy -- nice and clear? [18:53:40] <^demon> I'm in ur svn, trackin' ur revs. [19:02:54] robla: RoanKattouw: ^demon: Reedy: short and sweet? http://etherpad.wikimedia.org/C2oyjZgcxb ? [19:03:04] hexmode: "post118deploy" is fine. can you plan a date that you'll switch those over to "1.18wmf1"? [19:03:11] *robla looks at etherpad [19:03:42] robla: sure, lemme look at the current schedule [19:03:43] <^demon> Common sense, yes? [19:03:43] I wouldn't require going through a single person before tagging 1.18wmf1 [19:04:01] Encourage people to only tag fixes for issues currently present in deployment [19:04:15] And whoever goes through the queue may kick things out with extreme prejudice if they're petty [19:04:17] RoanKattouw: a big part of why I said *WHO* ;) [19:06:19] <^demon> Well, anyone can tag anything, like Roan says :) [19:06:30] Yeah [19:06:30] <^demon> It's up to the person doing the merging to use judgement. [19:06:43] <^demon> I should hope our mergers aren't doing blind merges anyway ;-) [19:06:47] Reedy: please say what you mean by "118ok" on the pad [19:06:59] yes, and I'm imploring the people who do merges (*ahem*) to please be very conservative [19:07:23] *especially* today [19:07:50] hexmode, I was just verifying [19:08:20] :) [19:08:44] ok, I've got to go pick up my daughter from school, back in 15-20 min [19:08:44] Oh, right, 1.18 deploy at 4pm [19:09:37] RoanKattouw: you'd forgotten about that? [19:09:56] <^demon> Maybe he just penciled us in :) [19:10:14] I'd forgotten which day [19:10:26] Today is a very exciting day, isn't it? [19:10:35] We've had two outages and a JS breakage [19:10:40] I'm probably about to break more minor things [19:10:46] yeah, I know [19:10:48] And 1.18 will probably break more minor things as well [19:11:24] and because we're doing everything at once, we won't know what is actually because of 1.18 [19:11:30] you got it [19:11:35] Eh? [19:11:51] <^demon> Today's turning out to be rather exciting indeed :) [19:12:42] alright, we've gotta sort out what we mean by "1.18ok" [19:13:04] <^demon> It only appears to apply to poolcounterd. [19:13:14] <^demon> Which, unless Tim's recompiling and deploying, won't affect anything. [19:13:30] ohhhh......right, ok, I remember now [19:13:56] we shouldn't be marking anything since the 1.18 branch point as 1.18 ok [19:14:12] <^demon> Yeah, I think we can just retire the tag except for those two revs. [19:15:06] Reedy: sorry for being cranky about 1.18ok....I'd forgotten how we were using that [19:15:41] Haha, it's fine [19:15:49] just thought it was worth being thorough [19:36:13] k, I'm back and not pinging ^demon [19:36:25] nice [19:37:34] I'd like to avoid listing tags in this email that don't have a description... ok to remove post1.18, 1.18revert and reverted1.18? [19:37:50] post1.18 I plan on making disappear anyway [19:39:22] or fix it? [19:40:18] Reedy: yeah, was thinking of just copying the description from the mw page [19:42:16] hexmode: would probably also be good to fix the mw page [19:42:33] will do [19:45:42] hexmode: the mail looks fine to me. I'm heading to lunch now [19:46:03] k, sending :) [20:11:37] updated mww page [20:21:07] I can't even follow #mediawiki now [20:21:36] *hexmode peeks at #mediawiki [20:35:51] Oh ffs [20:35:56] Where is