[02:12:44] I think VE is throwing an HTTPS warning... [02:14:36] It is. [02:14:37] Silly. [02:19:46] VE? [02:20:00] Bsadowski1: = VisualEditor [02:20:05] AH. [02:20:09] Ah* [02:21:35] Oh, sorry. [02:21:40] Yeah, VisualEditor. [02:21:45] https://bugzilla.wikimedia.org/show_bug.cgi?id=49284 [02:21:54] No, https://bugzilla.wikimedia.org/show_bug.cgi?id=49283 [02:21:56] So many bugs. [04:46:34] just tried searching on mw.org: An error has occurred while searching: HTTP request timed out. [04:46:46] and it works now [08:10:40] question: do you guys know of a fatal exception that is thrown when hiding and unhiding edits? [09:02:32] Wiki13, bugzilla may know for sure:) [09:03:44] I´ve already searched, but I couldn´t find a bug that looks similiar to my problem :/ [09:35:31] zeljkof: just a heads-up, I guess you've seen https://bugzilla.wikimedia.org/show_bug.cgi?id=49294 ? [09:36:08] andre__: thanks, did not see it [09:36:23] but QA team has it's own Jenkins, so we do not care :) [09:36:40] oh, didn't think about that :) [09:36:58] wondering who else to ping then. maybe wait for hashar... :-/ [09:37:11] hasher would be one to ping [09:37:14] yeah [09:37:16] but I do not see him here [09:37:20] Wiki13: I'm not aware of any bug report about it - could you file one with good info? See https://www.mediawiki.org/wiki/How_to_report_a_bug [09:37:58] ok [09:38:12] I´ll report one than [09:38:42] like steps to reproduce, exact output, and where it happens [09:39:16] ssl_error_bad_cert_domain on https of bugzilla btw [09:39:17] o.o [09:40:28] what product do I need to choose? [09:40:42] just mediawiki? [09:46:04] Wiki13, I'd say so for the start [09:54:30] andre__: https://bugzilla.wikimedia.org/show_bug.cgi?id=49301 [09:56:41] thanks [10:13:23] andre__: WMF Engineering Google calendar says hashar is on vacation, if Jenkins problem is a big one, someone should probably call or text him [10:14:06] mhm [10:14:16] zeljkof, I've CC'ed greg-g on https://bugzilla.wikimedia.org/show_bug.cgi?id=49294 , hoping that he can find somebody to take care of it [10:14:23] it is tagged as dupe I see now andre__ [10:14:39] could´nt find that bug when I was searching for it [10:14:58] oh we talked about rev deletion. I was only looking for "hiding". [10:15:03] no problem, dups happen. [10:17:56] it seems to be reported quite early in the morning for me [10:22:11] i was editing that bug too lo [10:22:13] l [10:22:49] got a ¨edit conflict¨ or mid-air collision how bugzilla calls it ;-) [10:27:40] hi [10:28:06] in DE-WP we get an Fatal exception on revdel and OS [10:28:24] Internal Error: [0176f3d5] 2013-06-07 09:57:56: Fatal exception of type MWException [10:28:30] is this bug known? [10:28:53] yes [10:29:13] https://bugzilla.wikimedia.org/show_bug.cgi?id=49290 [10:29:30] ah ok fine, thx [11:50:43] Hi [11:51:31] I got an internal error after using the REVDELETE option (on it.wiki) [11:51:56] "[e1a4cb53] 2013-06-07 11:22:56: Fatal exception of type MWException" [11:52:05] supernino_: its a known issue [11:52:28] It happens since today [11:54:19] Oh, ok "Bug 49290". I'm reading about it now [11:54:31] thanks [11:54:33] ah, major bugs on fridays. [11:55:02] hey, it's domas, just in time to save the day [11:55:07] whatsup [11:55:20] domas: where do you want to start? >.> [11:55:23] https://bugzilla.wikimedia.org/show_bug.cgi?id=49290 :P [11:55:50] (and a bunch of other stuff, too) [11:58:00] hmm [11:58:04] https://bugzilla.wikimedia.org/show_bug.cgi?id=49303 looks interesting [11:58:08] "Revision deletion of an unreviewed change raises MWException" [11:58:17] so i guess hoo broke it. :P [11:58:38] ah, wait, that's pending changes, not patrolling [12:07:59] well [12:08:13] do you want me to teach how to instrument the system to find problems like this? [12:21:57] 2013-06-07 11:22:56 mw1079 itwiki: [e1a4cb53] /w/index.php?title=Speciale:CancellaRevisione&action=submit Exception from line 178 of /usr/local/apache/common-local/php-1.22wmf5/includes/Hooks.php: Invalid callback in hooks for ArticleRevisionVisibilitySet [12:22:39] MatmaRex: it's Parsoid [12:22:40] Again [12:22:59] $wgHooks['ArticleRevisionVisibilitySet'][] = 'ParsoidHooks::onRevisionDelete'; [12:23:08] Should be onArticleRevisionVisibilitySet [12:25:01] who to blame... [12:25:05] Gabriel or Aaron? [12:29:24] Nothing in the log for the other one [12:33:53] Reedy: domas, of course. [12:34:19] also thanks for looking into it [12:34:23] hehe [12:34:48] We have far too many extensions [12:35:40] hopefully we'll be able to kill of Vector soon [12:35:58] off* [12:36:22] 1 in 557 is going to make no difference [12:36:48] well, not all 557 are deployed [12:36:56] But i have all 557 checked out [12:38:33] doing misc stuff now [12:39:03] apparently there are 98 extensions deployed on en.wp [12:39:11] i didn't realize there are this many [12:40:16] We branch nearly 160 for wmf usage [12:45:14] 1 bug fixed [12:46:33] MatmaRex: Those bugs were the same thing [12:58:00] Reedy: yay. now fix jenkins, you mage. :D [15:10:48] Commons is somewhat broken right now. [15:11:07] it's giving a lot of 503 errors. [15:11:26] ragesoss: well, it's an exciting friday for sure [15:11:41] :) [15:11:53] lots of stuff was broken earlier, too [15:12:04] (but got fixed) [15:14:08] Whilst doing what ragesoss? [15:14:55] Reedy: when trying to access the full version of a file, sometimes. Such as http://upload.wikimedia.org/wikipedia/commons/3/3c/Wikimedia_Commons_web.pdf [15:15:22] see also http://commons.wikimedia.org/wiki/Commons:Village_pump#.22Error_503_Service_Unavailable.22_when_trying_to_access_images [15:16:02] apergos paravoid AaronSchulz ^ for starters.. [15:16:20] mark is doing some changes [15:16:22] we know [15:16:30] mark is breaking shit :P [15:16:35] should come back now [15:16:54] I'll post to the Commons VP that you're on it. [15:20:07] :) [15:20:52] thanks ragesoss :) [15:21:44] right now I am getting an interesting rendering error on enwiki: Failed to parse (Cannot store math image on filesystem.): \{ A, B, C, D \} [15:23:38] hey [15:26:33] carl-cbm: hey, that's the fourth bug today, i think [15:27:18] I suspect that's likely related to the 503s above [15:27:49] Can anyone help me with my own deployment of wikimedia? [15:27:59] problem I've been staring at for weeks [15:28:30] and It occurred to me rather than trying to reverse engineer it and figure out it's probably something that comes up quite often [15:28:31] You're likely mixing terms there, but it is also offtopic in here [15:29:06] module code not parsing isn't a technical issue? [15:29:58] What module code? [15:30:25] And yes, it mgiht be, but if it's not on wikimedia wikis, it's somewhat offtopic, and even then #wikimedia-dev is likely a better place [15:31:23] so this is a channel exclusive to the wikimedia wiki, Fair enough. Thanks for the headsup [15:55:44] Hellow everybody [15:56:09] I think to begin a Mediawiki commons gadget, what is the best way to begin? [15:56:32] I am javascript/jquery/whatever programer [15:56:50] thanks [15:57:19] whatever programmers are so hard to find these days. ;) [15:57:29] wilfredor, you can also try asking in #mediawiki [15:57:58] Theo10011: yes, but I want to test my future gadget over some wikimedia project, especificly commons [15:58:25] Theo10011: whatever like any framework :p [15:58:31] well there is a commons channel, #wikimedia-commons but I'm not sure you'll get the right technical advice there. [15:58:45] wilfredor, I know. I was just kidding. ;) [15:59:02] Theo10011: :) [15:59:22] Theo10011: the commons channel is a user channel [15:59:50] Yes, I realize that. But -tech channel isn't very active either. :( [15:59:56] You might have to wait to get a reply. [16:01:22] Theo10011: however I will wait here :D [16:03:31] wilfredor: the place to start is probably by building the features you want on a .js page in your userspace. [16:04:37] wilfredor: check out https://commons.wikimedia.org/wiki/Commons:User_scripts [16:04:38] wilfredor: Are you looking for the opinion of a MediaWiki developer or are you also interested in my opinion? [16:05:06] And are you familar with the mw-object? [16:05:31] If not, see http://www.mediawiki.org/wiki/RL/DM [16:06:56] wilfredor: Which kind of gadget would you like to start? A library, a complex user interface or "just a link"? [16:20:54] no response --- quitting in 60s [17:38:35] hey andre__ [17:40:13] m [17:40:17] I am back [17:40:26] rillke is not online [17:40:44] ragesoss: Thanks interesting [17:41:13] rillke knows more than I do about developing gadgets on Commons. [17:41:39] note that he's one of the people listed on the userscripts page to go to for help. :) [17:43:03] but in general, you can start by developing a gadget as a userscript. Then once it's mature, you can try to get it through the requirements to become an actual gadget accessible through preferences (if that's your goal) [17:58:48] ragesoss: Do you know some How to? [17:59:10] ragesoss: step 1, 2, 3 [17:59:37] ragesoss: because I only need to know the user page to make the js and the configuration to call the script [18:00:25] wilfredor: you can create the script somewhere like User:Wilfredor/myscript.js [18:00:42] ragesoss: ok and step 2? [18:00:52] and you can load the script by adding a line to import it to User:Wilfredor/vector.js [18:01:10] wilfredor: see for example http://en.wikipedia.org/wiki/User:Sage_Ross_%28WMF%29/vector.js [18:01:58] the English Wikipedia pages about userscripts may have more useful info for youhttp://en.wikipedia.org/wiki/User:Sage_Ross_%28WMF%29/vector.js [18:02:02] ragesoss: and where I could to se the script runing? [18:02:09] whoops [18:02:10] http://en.wikipedia.org/wiki/Wikipedia:Userscripts [18:02:25] wilfredor: it would affect your own account. [18:02:58] "Gadget" has a specific meaning in mediawiki, and I realize now that you might have something else in mind. [18:03:04] http://en.wikipedia.org/wiki/Wikipedia:Gadget [18:03:57] ragesoss: yes I underestand [18:04:06] ragesoss: some hellow wolrd over there? [18:05:33] wilfredor: try browsing some of the existing scripts, and you can install any of them to see how they work http://en.wikipedia.org/wiki/Wikipedia:WikiProject_User_scripts/Scripts#Scripts [18:06:56] ragesoss: well [18:09:36] ragesoss: Nice! :D [18:10:06] ragesoss: I think to do a QI image review tool [18:10:24] sounds like a good project! [18:11:49] ragesoss: Yes, The QI review process is very stupid, we need a tool to do that faster [18:13:06] ragesoss: It run HTML5 ? [18:13:59] wilfredor: I'm not sure how much HTML5 stuff you can do through userscripts/gadgets. [18:14:12] ragesoss: do you know some example to edit a page section by ajax ? [18:17:21] ragesoss: I need to do a replace in a article section in background [18:18:12] ragesoss: 404 https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/core.git;a=blob;f=resources/mediawiki.api/mediawiki.api.edit.js;hb=HEAD [18:18:47] gitweb is dead [18:19:14] well, we need update http://www.mediawiki.org/wiki/RL/DM [18:19:28] ragesoss: http://www.mediawiki.org/wiki/API:Edit [18:21:13] ^demon was working on redirects [18:23:18] I'm trying to edit a section on a page on Wikipedia, but when I do so the whole section gets replaced by whatever text I send through the URL, even the heading, so it stops being a section. Is there any way to edit a section without deleting the heading? [18:23:41] full code here http://stackoverflow.com/questions/12518980/mediawiki-api-edit-section-without-destroying-heading [18:26:52] wilfredor: well, then add the heading to your wikitext? [18:27:31] MatmaRex: some idea? [18:27:44] MatmaRex: https://commons.wikimedia.org/wiki/User:Wilfredor/test.js [18:27:57] wilfredor: i don't see what the issue is [18:28:08] wilfredor: if you're overwriting the wikitext, the old one will disappear [18:28:16] API section editing works just like normal section editing [18:28:45] wilfredor: so you need to include the heading syntax in the wikitext you're saving [18:30:17] M_M [18:36:38] MatmaRex: how to know a section by name? [18:41:34] wilfredor: there's an API to return a list of all section on a page, ithink [18:41:36] like a toc [18:42:32] (looking for it) [18:43:14] wilfredor: action=parse&prop=sections [18:52:13] MatmaRex: maybe mw.util.getParamValue( 'section' ); [18:53:14] wilfredor: …what are you trying to do? [18:53:57] MatmaRex: my code is https://commons.wikimedia.org/wiki/User:Wilfredor/test.js [18:54:15] MatmaRex: I want to add +1 to section counter in https://commons.wikimedia.org/wiki/User:Wilfredor/test [18:55:30] MatmaRex: or simply replace a text in counter section [18:57:03] wilfredor: and what are you having issues with? [18:57:09] wilfredor: do you know how section editing works normally? [18:57:24] wilfredor: namely, how the heading is included in the section? [18:57:30] it's exactly the same when doing it via API [18:57:38] MatmaRex: I need the integer section number, I need a formule to know the edit section by name [18:58:02] wilfredor: the section number here is '1', as this is the first section [18:58:05] or do you mean in general? [18:58:05] MatmaRex: no I dont know, do you have some sample? [18:58:18] MatmaRex: in general [18:58:41] action=parse&prop=sections [18:59:13] wilfredor: https://commons.wikimedia.org/wiki/Special:ApiSandbox#action=parse&format=json&page=User%3AWilfredor%2Ftest&prop=sections [18:59:33] wilfredor: the '1' you're looking for is 'index', i think [19:00:11] wilfredor: then you can use action=query&prop=revisions to retrieve the wikitext [19:00:17] MatmaRex: in this case is 1, but I need to get the 1 by the section name, because the source is for a general propose [19:02:15] wilfredor: the section name is included in the api output [19:02:19] wilfredor: as 'anchor' [19:02:41] (okay, it's not exactly the section name - it's the url-anchor-encoded section name, but it's close enough) [19:02:51] or maybe 'line' is the name [19:57:43] ^demon: would it be possible to do the git migrations partially, keeping a note '' in the repositories, so we can do some iterations? [19:57:47] for pywikipedia [19:58:10] <^demon> Hmmm, could get messy. [20:00:56] ^demon: on the WMF end or on the 'people submitting patches' end? [20:01:41] <^demon> Yeah. If people submit patches and then we end up re-migrating, the commits would either get lost or have sha1 mismatches. [20:02:23] Sure. On the other hand, it would allow to have a relatively simple way to test the migration, nightly scripts, etc. [20:02:33] as well as to get comments on the way the migration is done [20:02:46] <^demon> Hmm, well what we could do is just migrate the code, but close it to patches. [20:02:55] that would be a good option, I think [20:03:06] <^demon> So people still use svn until $cutoverDate, but allows for swapping things like scripts and so-forth. [20:03:21] exactly [20:03:29] plus it allows fiddling with the migration [20:03:39] e.g. splitting branches differently, etc [20:04:59] <^demon> And if we have to rewrite history, no big deal :) [20:05:03] <^demon> Since nobody's put patches in. [20:05:22] exactly [20:05:30] <^demon> Ok, well if those rules on-wiki are sane, I can go ahead and do this monday. [20:05:45] <^demon> Or maybe over the weekend, not doing much :) [20:06:39] How painful are git submodules in practice? [20:06:54] Deleting them is the hardest part [20:07:01] git doesn't like that much [20:07:49] <^demon> Using them isn't all that hard. [20:08:25] <^demon> valhallasw: We've been using them for some time now for the extensions on WMF branches. [20:08:32] <^demon> Never really had much of a problem. [20:09:22] OK. [20:30:23] ^demon: I added a new possible structure to the wiki page and sent an e-mail with some notes & proposed transition schedule. [20:30:33] <^demon> Ok, will take a look in a bit [20:31:20] thanks! :-) [20:32:58] robla: what is an 'oboarding tutorial'? :-) [20:33:37] (re: engineering roadmap update) [20:34:25] hi valhallasw: about to head to a meeting. Short answer is if that's in ECT, it's probably something sumanah can answer [20:36:47] Sure. thanks. [20:44:50] why is that when opening some special pages, guided tours is activated? [20:45:05] is there any bug reported yet? [20:46:16] I'm looking for a list of the "disambiguation" tag names for each language. Ayone know of such a thing? [20:47:59] Alchimista, what guided tour? Can you give an example? It's either driven by a ?tour URL parameter or a tour cookie [20:48:48] Alchimista -mw-tour [20:48:49] sigh [21:21:27] ^demon: oh, you fixed git.wikimedia.org on HTTP? [21:22:33] <^demon> I didn't know it was broken... [21:22:37] <^demon> It's been redirecting since start. [21:23:31] ah, at least some URLs were broken for me [21:24:10] http://git.wikimedia.org/summary/mediawiki%2Fextensions%2FMathSearch.git [21:24:30] but works on https [21:24:40] that's just first random link I clicked [21:24:44] <^demon> Yeah, all http should redir to https. [21:24:56] that one doesn't [21:40:43] <^demon> Nemo_bis: Does for me... [21:40:56] A user has reported a problem with trying to submit an article to http://en.wikipedia.org/wiki/Education_Program:University_of_California,_Los_Angeles_%28UCLA%29/146B_%28Spring_2013%29 [21:41:26] They get the "Our servers are currently experiencing a technical problem." message. Is this the right place to report that? [21:44:57] 9 PHP Catchable fatal error: Argument 1 passed to ManualLogEntry::setTarget() must be an instance of Title, null given, called in /usr/local/apache/common-local/ [21:44:57] php-1.22wmf5/extensions/EducationProgram/includes/Utils.php on line 32 and defined in /usr/local/apache/common-local/php-1.22wmf5/includes/logging/LogEntry.php on line [21:44:57] 394 [21:45:06] wolfgang42: I think that's a known issue with an unreviewed fix. [21:47:04] Ah, OK [21:49:25] Hmm. Or has it been merged... [21:50:14] It has been [21:50:19] Let's fix this up in production [21:58:08] wolfgang42: Try again [22:04:33] Reedy: I can't, the person left long ago. [22:04:42] But thanks anyway! [22:56:39] at nl-wiki we have a bug in the patrol system [22:58:27] Romaine, what is the bug? [22:59:02] patrol system currently has several bugs [22:59:12] which of course can as well be considered features [23:01:30] for some reason the mark new article as read is showing up on the bottom of older articles and clicking on them doesn't have much affect [23:01:39] on bottom: https://nl.wikipedia.org/wiki/Wereldkampioenschappen_veldrijden_2004 [23:01:41] as example [23:01:55] between the navbar and the category bar [23:02:04] [Dit artikel als gecontroleerd markeren] [23:02:18] this is usually only shown on a new article to be marked as patrolled [23:02:34] also some texts in the sidebar are in English [23:08:52] Romaine: for the sidebar, there are 1495 and friends (one dependency was just reopened by a nl.wiki user= [23:10:28] Romaine: for the article, that's a recent one and the button will patrol the last revision; it doesn't work for you because it's an edit by you [23:11:24] I noticed this earlier today as well, the button is not hidden if you can't edit it; however there's another patch under review and another request without patch that may affect this too, maybe bawolff would understand [23:12:02] * bawolff looks [23:14:57] Nemo_bis: still it is not correct, we normally have never such mark as pattrolled buttons at the bottom of pages, only for new articles [23:15:26] other mark as patrolled are normally only in diff pages [23:15:32] I know, I know [23:16:03] Romaine: So to clear, you think having both types of patrol directly on the page would be a "bug" not a "feature"? [23:16:11] Romaine: for now everyone agrees on https://bugzilla.wikimedia.org/show_bug.cgi?id=49115 to start with [23:16:19] it is serieously a bug yes [23:17:19] Nemo_bis: What? [23:17:36] Er, sorry. I thought you were pinging me. Nevermind. [23:17:47] I kind of wish that https://gerrit.wikimedia.org/r/#/c/67040/ only did the message change. I think the other part of that change is more debatable [23:18:17] meh, its better than the current situation [23:18:22] * bawolff goes to review that patch [23:23:53] whoops, I had introduced a mistake in the commit message [23:31:22] the boolean conditions in the if statement in that patch is screwing with my mind [23:32:27] if we know its not new page patrollable and ( we are not using rc patrol or we know its not rc patrollable) then do nothing [23:32:38] hmm, that makes much more sense when I write it in english