[01:23:09] What exactly is the difference between subst: and safesubst: [01:24:06] https://en.wikipedia.org/wiki/Help:Safesubst#safesubst [01:24:37] any interface editors or stewards home? (or sysadmins for that matter) [01:24:58] legoktm: I've read that a dozen times, and I still don't see difference. Can you summerize for me? [01:25:24] need to revert to https://hy.wikipedia.org/w/index.php?title=MediaWiki:Common.js&oldid=1327439&uselang=en per http://lists.wikimedia.org/pipermail/wikilovesmonuments/2013-September/006676.html [01:25:38] jeremyb: #wikimedia-stewards [01:26:00] legoktm: yeah, this is just the first place i tried, not last :) [01:26:17] as I just wrote in #wikilovesmonuments: no one responded defending or explaining the tool and the guy that originally announced it on the list was CC'd explicitly on my message [01:26:24] now to #-stewards :) [01:27:27] Just recursion? [01:28:01] Technical_13: huh? [01:28:30] What exactly is the difference between subst: and safesubst: [01:28:44] oh. different convo [01:28:58] Just that safesubst can be used recursively. [01:29:05] That's all I see [01:29:16] i don't remember. i think most of my template work predated safesubst: [01:29:18] maybe [01:39:20] Technical_13: "subst" only works during the pre-save transform, and breaks the transclusion if it manages to exist outside that stage. "safesubst" works like "subst" during PST but still allows transclusion in later parsing stages, so something like safesubst: actually works right. [01:39:59] (i.e. it substs when the containing template is substed and transcludes when the containing template is transcluded) [01:46:27] anomie: no special bits, right? (staff?) [01:48:16] jeremyb: If you ask me in my staff capacity, I have no special bits (besides non-root shell access to fluorine, terbium, tin, and so on). If you ask me as a volunteer on enwiki, I have the admin bit. [01:48:34] hrmmm, i need hywiki though [01:48:49] thanks anyway :) [01:49:42] anomie: log has the reason shortly before you joined. http://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-tech/20130916.txt [01:49:45] back in a bit [01:52:13] Bsadowski1 says he's looking into it [01:52:26] ? [01:52:31] What? [01:53:33] no I'm not [02:10:39] ok, nvm, no one's looking into it. yet. [02:10:40] 16 01:52:44 < Bsadowski1> oh sorry [02:10:40] 16 01:52:54 < Bsadowski1> I thought you were LlamaAl [02:12:35] jeremyb: FYI, https://meta.wikimedia.org/wiki/Special:GlobalUsers/Staff has a list of people you could ask, if you know their IRC nicks. Also https://meta.wikimedia.org/wiki/Special:GlobalUsers/editinterface and https://meta.wikimedia.org/wiki/Special:GlobalUsers/Global_sysops [02:14:02] right, was looking at some of those before but i just got back to a computer so now i have to resume [03:58:04] jeremyb: why's the wiki slow/giving errors? [03:58:11] seeing no errors in -ops or here [03:58:12] "the wiki" [03:58:27] i just saved without a problem. well i guess a few mins ago [03:59:30] jeremyb: I wonder if 100% LVS usage is normal [03:59:36] that's what I currently see on ganglia [03:59:42] link? [03:59:46] http://ganglia.wikimedia.org/latest/?c=LVS%20loadbalancers%20eqiad&m=cpu_report&r=hour&s=by%20name&hc=4&mc=2 [04:00:00] I somehow don't htink it should be that high [04:00:31] but all the LVS's have high CPU despite low load [04:01:24] where do you see the cpu being high? [04:01:33] sure you're not looking at the "idle" value? [04:02:14] * Jasper_Deng_busy is [04:02:25] not accustomed to reading this gr aph [07:58:07] hello all [08:00:31] hello cff [08:00:56] cortexA9: hey [11:05:08] apergos: hello [12:22:44] that will teach me to take my lunch break away from the keyboard [12:23:04] I've been watchig the test run, we're at about 5.3 gb now [12:23:23] the next tests I'll run on something smaller so I can get an immediate sense of the impact on the nfs share [12:23:30] that will teach me to take my lunch break away from the keyboard and see how I can mitigate that, that's not work for you [12:23:50] ok [12:24:20] i was wondering, are going to test that the dump is actually okay and that it generates the correct XML? if so, how? [12:24:45] well converting it back willl let us know something [12:25:05] we can check that all the titles and texts are identical [12:25:12] we can check that revids are identical [12:25:21] it really shouldn't be too bad [12:25:24] because the original XML and the regenerated one won't be the same byte by byte (mostly because of the revision order) [12:25:32] not too worried about that [12:25:37] ok [12:27:25] hmm, i started working on compressing comments today [12:27:47] great [12:27:48] but maybe it would make more sense to do progress reporting for idumps create first? [12:27:58] if it's short [12:28:16] yeah, it shouldn't take long [12:28:23] great [12:34:16] i can't think of anything else, what about you? [12:36:25] surprisingly... nope [12:36:32] it's all about testing things from my end [12:36:58] yeah, hopefully, it will go well, [12:37:07] if not, let me know [12:37:07] if not, that's what tests are for [12:37:20] yep, as soon as I have a better handle on the disk-related issues [12:37:48] ok, see you tomorrow then [12:38:11] see you :-D [18:08:03] any reason db1005 is so lagged? [18:09:15] It's pretty idle [18:10:40] Reedy: its showing a 16126 second lag [18:11:27] 14999 [18:11:35] it's dropping fairly quickly now [18:11:42] there were some slave threads waiting [18:12:36] 14053 [18:29:30] Did we just deploy something login related? [18:31:54] Just got an error that was unfamiliar to me, will see if it reoccurs [18:33:32] Looks like someone else just had a login related problem as well [18:35:39] jarry1250: where? error message? [18:36:18] greg-g: Despite having just initiated the login, I got an error served by login.wikimedia.org, token expired (or words to that effect) [18:36:34] csteipp: ^^ [18:37:43] Are we having memcache issues? [18:38:14] The report on VPT seems a little different. Nothing awful, but just thought I mentioned it, given the importance of logins [18:38:46] jarry1250: which vpt? enwiki? [18:39:04] csteipp: Yes [18:40:37] csteipp: I may also have been logged into Commons, which just went to 1.22wmf17 around the time of the issue (but I was trying to log in from enwiki) [18:40:46] (so I guess I was logged in on neither) [18:57:46] and now it's slow as helllllll [18:59:22] thedj: I thought that was just my crappy laptop :P [19:00:20] getting better. guess something was getting deployed. [19:02:37] rofl "Next semester I am teaching a library technology course� �what should I cover? " [19:02:41] "Just project the Wikipedia homescreen and weep for the entire semester, mumbling, "We're doomed, DOOMED!"" [19:14:41] Anyone else having trouble with ESAMS this evening? It seems my packet loss is hovering around 15% all evening. [19:17:27] Excirial: Can you post a traceroute for our network guys to have some idea how you're reaching us [19:17:28] mark LeslieCarr ^ [19:17:38] (to a pastebin, of course) [19:18:04] Sure, no problem. [19:49:11] If someone gave that load balancer a nudge: Great job. Packet loss jolted back from 12% to ~3% over the last 10 minutes. [19:51:16] -3% ?! it's adding free packets! woo! A packet for you, a packet for you, a ... [19:51:52] oh, that's a tilde, not a minus. damnit. [19:53:39] quiddity, your wuid was trying to bring back additional energy/matter from the past I see [19:53:43] *quid [19:53:45] network issues are being worked on [19:56:04] so not 3% [20:23:28] :-/ [20:28:11] ? [20:42:23] csteipp: ping [20:43:21] Just got redirected to https://wikimediafoundation.org/wiki/Special:CentralLogin/start?token= during login [20:43:38] ...which errors [20:44:34] My login had timed out [20:49:08] jarry1250: known bug, found it? [20:49:28] https://bugzilla.wikimedia.org/show_bug.cgi?id=52206 [20:50:53] Nemo_bis: Thanks [21:26:41] YuviPanda: ping [21:29:37] dMaggot: pong [21:30:56] YuviPanda: I'm retaking my pending work on the select widget patch for UploadWizard [21:31:13] YuviPanda: I'm ready to submit a review removing the commented code I introduced with that patch [21:31:20] dMaggot: wooo, nice [21:31:24] do add me as reviewer! [21:31:25] YuviPanda: just waiting for ori-l to review https://gerrit.wikimedia.org/r/78641 [21:32:04] dMaggot: I'll review today; sorry for the delay. [21:32:20] ori-l: no problem [21:32:25] YuviPanda: after that's taken care of, my question is can you elaborate on the comment at... [21:32:39] comment at? [21:32:48] YuviPanda: sorry, ori-l's pending review is https://gerrit.wikimedia.org/r/84011 [21:33:39] YuviPanda: the comment saying "However, one concern is that the 'list of items' cannot be localized. I think that is okay for now, but we should figure a solution out at some point." [21:34:15] YuviPanda: how do you see these items being localized? through the json itself or using something at client/server level apart from the json values? [21:34:16] dMaggot: ah, yes. that. [21:34:36] dMaggot: so that is what I do not know [21:34:36] dMaggot: i think it is fine to let them be not localized for now [21:34:36] putting all of those in JSON feels like overkill to me [21:34:54] dMaggot: eventually, we should be able to pull these from another source - like wikidata. Eventually as in in a year's time or so [21:36:52] YuviPanda: ok, then that's in standby for now [22:02:16] dMaggot: indeed. [22:02:24] dMaggot: we can fix that eventually, but not right now [22:40:10] FYI: [22:40:10] Request: POST http://meta.wikimedia.org/wiki/Special:MovePage/Tech/News/2013/35, from 208.80.154.77 via cp1009.eqiad.wmnet (squid/2.7.STABLE9) to 10.64.0.138 (10.64.0.138) [22:40:10] Error: ERR_READ_TIMEOUT, errno [No Error] at Mon, 16 Sep 2013 22:37:13 GMT [22:40:23] While trying to rename a page managed by Extension:Translate [22:55:06] guillom: You broke it. [22:55:15] https://bugzilla.wikimedia.org/show_bug.cgi?id=53769 [23:53:54] gn8 folks