[08:46:19] [[Tech]]; Mathonius; /* Luxotool/guc */ re; https://meta.wikimedia.org/w/index.php?diff=6253817&oldid=6250552&rcid=4649415 [08:49:43] [[Tech]]; Mathonius; /* Luxotool/guc */ +; https://meta.wikimedia.org/w/index.php?diff=6253864&oldid=6253817&rcid=4649430 [08:52:34] [[Tech]]; Luxo; /* Luxotool/guc */; https://meta.wikimedia.org/w/index.php?diff=6253890&oldid=6253864&rcid=4649432 [10:33:40] @seen bwaolf [10:33:40] Steinsplitter: I have never seen bwaolf [10:33:54] @seen bawolff [10:33:54] Steinsplitter: Last time I saw bawolff they were quitting the network with reason: Quit: Bye N/A at 11/3/2013 1:00:03 AM (1d9h33m50s ago) [10:34:44] where is the right place to report issues with the ApiSandbox extension? I believe that the introductory message is grossly misleading [10:36:57] skalman12: bugzilla.wikimedia.org, product "Mediawiki Extensions", Component "ApiSandbox" [10:38:12] YuviPanda: thanks! [10:38:16] yw :) [10:50:36] another question: how do you use mw.loader.using if I have two dependencies? [10:52:48] git.wikimedia.org giving 500 today? GET http://git.wikimedia.org/, from 127.0.0.1 via cp1044 cp1044 ([127.0.0.1]:80), Varnish XID 1195466591 [10:52:51] Forwarded for: 2a01:198:200:15f::2, 127.0.0.1 [10:53:03] Error: 500, Internal Server Error at Mon, 04 Nov 2013 10:52:06 GMT [10:55:30] saper: heh, file a bug, probably OOM'd again [10:55:34] saper: also, use GitHub :D [10:55:50] okay, I really should go away and sleep [10:57:16] skalman12: mw.loader.using(['dependency1', 'dependency2'], function(){}) [10:57:38] MatmaRex: thanks - I couldn't find documentation on that [11:18:46] YuviPanda|away: thans, filed bug 56557 [15:08:38] sjoerddebruin: Hi [15:08:51] Hi Krinkle. Did you saw my message? [15:10:16] sjoerddebruin: Ja [15:10:33] sjoerddebruin: Komt mogelijk door een trage reactietijd van de server. Ik ben het momenteel aan het onderzoeken. [15:10:42] sjoerddebruin: Lijkt het browseronafhankelijk? [15:10:52] In de Tech-nieuwsbrief stond trouwens ook dit:Due to a recent change, gadgets and user scripts that use jQuery UI should explicitly load the appropriate modules, as they may not be loaded by default. [14] [15:10:53] Developers have started to remove long-deprecated methods. You should check the JavaScript console (in debug=true mode) and look for deprecation warnings and their stack trace. [15:11:02] Weet ik niet, grmbl had er ook last van [15:27:08] sjoerddebruin: Heeft daar niks mee te maken. [15:27:22] Oh oke [15:27:22] sjoerddebruin: Dit is een server probleem, niet in de gadget of javascript [15:27:46] Irritand. [15:27:48] sjoerddebruin: Is nu opgelost. Er zat een kapotte server in de roulatie. Deze heb ik eruit gegooid. [15:27:57] sjoerddebruin: Is het beter nu? [15:28:05] Ja hij werkt weer [15:28:10] :) [15:28:29] sjoerddebruin: Bedankt voor je raport. [15:28:43] Kon ook wel een bug aanmaken eigenlijk... [15:30:11] Volgens grmbl deed die het vanmorgen wel Krinkle [15:30:14] Maar na 12:00 niet meer [15:45:24] Admins on wp.fr can't restore or read versions of some deleted pages : https://fr.wikipedia.org/w/index.php?title=Sp%C3%A9cial:Restaurer&target=Programme_de_communication%2C_d%27%C3%A9ducation%2C_de_sensibilisation_et_de_participation_du_public and https://fr.wikipedia.org/w/index.php?title=Sp%C3%A9cial:Restaurer&target=Fr%C3%A9d%C3%A9ric_J._Duval [15:47:49] Frakir, can you be more specific? [15:49:01] There is no page history [15:49:49] (it is written that there is no page history*) [15:51:07] We discuss about this problem here https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Bulletin_des_administrateurs/2013/Semaine_45 [15:51:13] No solution [15:56:42] hmm. Maybe a Toolserver user can try to find the DB records [17:37:02] AaronSchulz: I was looking at Flagged Revisions. Would it be possible to have multiple editor/reviewer classes? [17:40:44] maybe, depending on what is meant [17:41:32] It's for a corporate wiki. Some people are responsible for some pages and want to keep control over it. [17:42:04] Say we have responsible A and responsible B. If someone edits responsible A's pages, responsible A should be able to review it, but not responsible B. [17:43:04] Say for example descriptions of standard changes. Changes management wants to be able to approve any changes to these pages. [17:43:37] are there different types of pages in different namespaces? [17:44:12] I could of course just create different namespaces, but that would be such a mess. Probably tagged with a certain template and tracked in a category. [17:44:43] ok, well, then you could also use ?action=stablesettings and some custom groups/rights [17:45:00] that way you could lock down some pages so only group A can review and others group B and so on [17:45:25] Ok. So this is all possible in the extension? That's nice to hear [17:45:28] or ?action=stabilize, whatever it's called [17:45:34] the rights for it is 'stablesettings' [17:45:37] ok [17:45:46] there is a link to it from the protection form [17:46:59] users with rights to that page but not ?action=protect will see a special tab for it too [17:48:08] And is it possible to add this protection to the page because it's in a certain category or tagged with a template? Something like cascading protection for the template? [17:53:58] AaronSchulz ? [18:10:26] multichill: maybe if you altered the default protection levels to add something on 'autoreview' (which effects 'review' too) you might be able to use cascade protection (changing $wgCascadingRestrictionLevels too) [18:10:57] How is it down with the living people articles on the English Wikipedia? [18:10:59] $wgRestrictionTypes / $wgRestrictionLevels / $wgCascadingRestrictionLevels [18:11:18] multichill: there is no blanked policy there, that's all per-page afaik [18:11:25] Oh, right [18:11:31] * multichill would be too lazy for that [18:24:13] greg-g: jdlrobson was wanting someone to deploy https://gerrit.wikimedia.org/r/93412 today; I'm game for doing it after my CN deploy if that's cool with you [18:24:40] thanks mwalker and no i don't have deploy access (btw is there a wiki who says who does?) [18:25:00] mwalker: cool [18:25:07] jdlrobson: it's the deployment group in gerrit [18:25:24] I checked there and was confused -- I was under the impression every wmf developer had deploy rights [18:25:33] does this group say who's best for certain types of deployment or are all deployers seen as equally useful? :) [18:25:59] all deployers are equally useful according to that list :p [18:26:12] or rather; it makes no declarations either way [18:27:12] which, is an assumption :) [18:27:37] https://gerrit.wikimedia.org/r/93412 is for the release branch [18:27:50] * aude wonders where the real patch is? :) [18:28:08] aude: https://gerrit.wikimedia.org/r/#/c/93408/ [18:28:14] ah ok [18:28:18] <^d> aude: Will the real patch please stand up? [18:28:43] :) [18:35:50] multichill: yes i did [18:35:55] multichill: what are you seeing now ? [18:36:24] multichill: actually yes *we* did --- as awesome as i am, i didn't do it alone [18:39:47] hey all, who are out toolserver admins? [18:40:25] russavia: I guess you want #wikimedia-toolserver [18:40:34] LeslieCarr: Ah, nice, let's see what mtr tells me [18:41:34] thanks [18:42:37] LeslieCarr: I see packetloss on 130.244.6.243. Last hop before sdtpa [18:43:21] Swip/tele2? [18:46:49] hrm [18:47:21] right before sdtpa? can you give me the traceroute and your ip (or ip block) [18:48:02] hrm so that's our router , tele2 transit port [18:48:26] it's not overloaded or showing errors, but we do rate limit pings and the like [21:56:31] greg-g: if I want to deploy my CentralNotice changes to all WMF branches -- what do I need to push changes to? 1.23wmf1 and 1.23wmf2? [21:56:50] mwalker: yessir [22:01:46] jdlrobson, MatmaRex: regarding the change you're having me push; will you be around in about 30 minutes to check that its working? [22:02:24] mwalker: sure just poke me then [22:02:37] you just need to try the print stylesheet [22:09:26] jdlrobson: does it go out to both 1.23wmf1 and 1.23wmf2 or just wmf2? [22:09:33] mwalker: yes please [22:09:35] both [22:12:49] ori-l: it looks like you have some pending changes in the wmf2 branch -- I can cherry pick my change; or rebase it all and push it all our [22:13:09] mwalker: it's safe to push out with your change; sorry 'bout that. [22:13:14] no worries [22:13:18] thanks [22:17:08] ori-l: pushed [22:18:45] thanks again :) [22:21:22] ori-l: feeling better today? [22:24:04] YuviPanda: so-so [22:24:11] ori-l: working from home? [22:30:10] so it seems like we have some data loss: https://bugzilla.wikimedia.org/show_bug.cgi?id=56589 and https://bugzilla.wikimedia.org/show_bug.cgi?id=56577 [22:30:26] greg-g, robla ^ [22:32:08] looking [22:34:30] andre__: just shared with MW Core [22:38:52] andre__: people are on it (looks like we can find the data, just needs a maintenance script, hopefully) [22:39:00] ah nice [22:39:10] jdlrobson, MatmaRex: now pushing your bugfix [22:41:10] I should have checked before I pushed it to see if there's been a difference [22:41:23] but... it doesn't, now, seem broken [22:42:33] mwalker: you haven';t synced Resources.php? [22:42:47] uh; do I need to? [22:43:04] only the .less files were touched in that commit [22:43:15] were they? oh [22:43:32] well, the change works? [22:43:38] why did you say it's broken :( [22:43:50] uh; I have no idea if the change works actually [22:44:05] it does for me [22:44:19] (Resources.php was touched in earlier version of that patch and i got confused, sorry) [22:44:32] I still have san-serifed fonts though [22:44:47] which, according to the bug report, is a part of the symptom [22:45:37] I'm sort of wondering if we need to manually compile those lss files [22:46:07] jdlrobson: ^ ? [22:47:31] no you don't [22:47:37] RL should do it on the fly [22:48:50] mwalker: then the bug is wrong [22:48:50] greg-g: I'm going to tentatively say I'm done -- at the very least things are not more broken than they were when I first started [22:49:05] mwalker: is the background of the entire page fully white #ffffff? if yes, it worked [22:49:06] heh; ok [22:49:18] (it something is beige, then it's broken) [22:49:39] MatmaRex: everything except the footer is white for me [22:49:45] the footer is still the desktop version [22:50:01] huh [22:50:12] mwalker: that's the most optimistic sentence I've heard [22:50:14] refresh the page? it's all white for me [22:51:03] MatmaRex: https://en.wikipedia.org/w/index.php?title=Marathon_de_La_Rochelle&printable=yes&debug=true [22:51:14] greg-g: I try to instill confidence [22:51:25] MatmaRex: is that all white for you? [22:51:35] mwalker: aaah, printable. hmmm [22:51:48] mwalker: i was using browser's "print preview" function [22:51:53] ah [22:51:57] ok; different problem there then :) [22:52:01] yeah, the footer there is broken [22:52:21] (it will be okay when printed, though) [22:53:17] i forgot we have that stupid thing [22:53:37] jdlrobson: ^ [22:53:50] this is why we can't have nice things [22:54:14] jdlrobson: so it seems like we can't do it this way, maybe we should split up the module again (the way it was before) [22:54:53] oh hey, new bug. thanks mwalker [22:55:09] np [22:55:45] okay, it's midnight here, and tomorrow i wake up at six. (or about.) [22:55:52] good night, have fun fixing bugs [22:56:00] (or cross-referencing them, if you could) [23:06:13] good night [23:10:38] [[2019_apres_la_chute_de_New_York]] is missing on all the s6 servers except the master [23:11:50] which is pretty scary [23:34:08] That is disturbing. [23:41:07] Grahhhhhhhhhhh. [23:41:49] wikitech.wikimedia.org is giving me fits of rage. [23:41:53] Is it down? [23:42:41] Yes [23:42:43] It's not just you! http://wikitech.wikimedia.org looks down from here. [23:42:51] seems to be [23:42:55] Hrmph. [23:43:15] I was idly wondering if the link on the mailing list led to a traffic spike. [23:43:19] And then it crashed. [23:43:20] But who knows. [23:43:22] chrismcmahon: is it possible to attach a debugger to the beta cluster? [23:43:52] I have an issue I cannot seem to reproduce locally -- but it is present on beta [23:44:16] live hack! [23:44:32] hehe [23:44:59] tempting [23:45:02] well, Ryan is on a flight... [23:45:36] If only the FAA allowed usage of electronic devices... [23:45:52] https://bugzilla.wikimedia.org/show_bug.cgi?id=56594 [23:45:57] Bugzilla is still up, don't worry. [23:46:07] is there documentation on mw.org about wikitech? I can't see to find it [23:46:14] Heh. [23:46:27] There are supposed to be offline copies of the wiki somewhere. [23:46:34] wikitech-static [23:46:41] no idea how current it is [23:46:43] https://wikitech-static.wikimedia.org/wiki/Main_Page [23:46:49] Go forth and static! [23:46:59] Interesting that that's on wikimedia.org. [23:47:13] I guess nobody is worried about DNS issues or something. [23:47:17] 24 hours out by the looks of it [23:47:31] Elsie: good point, maybe we should use wikia... [23:47:43] https://wikitech-static.wikimedia.org/wiki/Wikitech [23:47:47] Fuck yeah, adverts [23:53:32] mwalker: beta cluster is essentially production, but running master branch of everything. what exactly do you mean by "attach a debugger"? [23:55:17] Question: Is it likely that at some point the page title size limit will be configurable? [23:56:18] Why? [23:56:33] It's currently limited by the size of the field in the database. [23:57:00] chrismcmahon: literally that -- if xdebug is installed; set a breakpoint and step through to figure out why part of the mobile frontend doesn't seem to think it's in mobile mode [23:57:15] Reedy: yeah, I know. I read the discussion on wikitech-l, not understanding all of it. [23:57:40] greg-g, robla: Hmm, this is a new confluence of events. I can't load the SAL to see if any slave/master DB changes have been deployed lately. [23:57:45] s/new/nice/ [23:58:13] right [23:58:53] TimStarling: Can Sean (or Domas) be paged? [23:58:55] Reedy: the reason I'm asking is because the current size limit could become problematic for the future ASL WP. [23:59:16] no master switches or anything else relevant were logged at the relevant times [23:59:24] What is ASL WP? [23:59:29] American Sign Language [23:59:56] It can be extended. Not sure how much a DBA would like you for doing so