[00:12:28] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 120 minutes) Saramg (waiting 115 minutes) Joelp (waiting 112 minutes) Dp (waiting 111 minutes) [00:12:29] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 86 minutes) [00:26:00] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 134 minutes) Saramg (waiting 129 minutes) Joelp (waiting 126 minutes) Dp (waiting 125 minutes) [00:26:01] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 99 minutes) [00:39:28] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 147 minutes) Saramg (waiting 142 minutes) Joelp (waiting 139 minutes) Dp (waiting 138 minutes) [00:39:29] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 113 minutes) [00:52:56] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 161 minutes) Saramg (waiting 156 minutes) Joelp (waiting 153 minutes) Dp (waiting 152 minutes) [00:52:57] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 126 minutes) [00:59:41] What's the internal route to http://huggle.wmflabs.org/data/wl.php?action=read&wp=en ? [01:06:28] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 174 minutes) Saramg (waiting 169 minutes) Joelp (waiting 166 minutes) Dp (waiting 165 minutes) [01:06:29] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 140 minutes) [01:16:28] <^demon> When someone gets a chance to poke those 4 users waiting for shell, that'd be great. I've love to respond to an e-mail with instructions for peeps. [01:18:46] ^demon: what would they be doing wrong to trigger that? [01:19:30] <^demon> Not a clue. I just found out what their 4 usernames were, and saw they didn't have loginviashell yet. [01:19:36] <^demon> And then saw the bot pestering here. [01:19:57] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 188 minutes) Saramg (waiting 183 minutes) Joelp (waiting 180 minutes) Dp (waiting 179 minutes) [01:19:58] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 153 minutes) [01:21:08] Jasper_Deng: Do you know how to access *.wmflabs.org from inside? [01:21:22] a930913: I heard you use a SOCKS proxy for that, over an SSH session. [01:21:27] * Jasper_Deng doesn't know the complete details [01:21:50] Jasper_Deng: That would only be if I had access to *. [01:24:34] I could ssh tunnel out of labs, but that would be ugly and prone to breaking. [01:33:18] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 201 minutes) Saramg (waiting 196 minutes) Joelp (waiting 193 minutes) Dp (waiting 192 minutes) [01:33:19] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 167 minutes) [01:46:39] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 215 minutes) Saramg (waiting 209 minutes) Joelp (waiting 206 minutes) Dp (waiting 205 minutes) [01:46:40] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 180 minutes) [01:52:42] a930913: You can access tools.wmflabs.org at tools-webproxy, but I don't think there's a general scheme. [02:00:04] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 228 minutes) Saramg (waiting 223 minutes) Joelp (waiting 220 minutes) Dp (waiting 219 minutes) [02:00:05] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 193 minutes) [02:13:24] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 241 minutes) Saramg (waiting 236 minutes) Joelp (waiting 233 minutes) Dp (waiting 232 minutes) [02:13:25] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 207 minutes) [02:26:45] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 255 minutes) Saramg (waiting 250 minutes) Joelp (waiting 247 minutes) Dp (waiting 246 minutes) [02:26:46] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 220 minutes) [02:40:09] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 268 minutes) Saramg (waiting 263 minutes) Joelp (waiting 260 minutes) Dp (waiting 259 minutes) [02:40:10] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 233 minutes) [02:53:34] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 281 minutes) Saramg (waiting 276 minutes) Joelp (waiting 273 minutes) Dp (waiting 272 minutes) [02:53:35] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 247 minutes) [03:06:55] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 295 minutes) Saramg (waiting 290 minutes) Joelp (waiting 287 minutes) Dp (waiting 286 minutes) [03:06:56] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 260 minutes) [03:20:20] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 308 minutes) Saramg (waiting 303 minutes) Joelp (waiting 300 minutes) Dp (waiting 299 minutes) [03:20:21] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 274 minutes) [03:33:48] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 322 minutes) Saramg (waiting 317 minutes) Joelp (waiting 314 minutes) Dp (waiting 313 minutes) [03:33:49] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 287 minutes) [03:47:16] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 335 minutes) Saramg (waiting 330 minutes) Joelp (waiting 327 minutes) Dp (waiting 326 minutes) [03:47:17] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 301 minutes) [04:00:44] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 349 minutes) Saramg (waiting 344 minutes) Joelp (waiting 341 minutes) Dp (waiting 340 minutes) [04:00:45] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 314 minutes) [04:14:12] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 362 minutes) Saramg (waiting 357 minutes) Joelp (waiting 354 minutes) Dp (waiting 353 minutes) [04:14:13] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 328 minutes) [04:27:36] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 376 minutes) Saramg (waiting 370 minutes) Joelp (waiting 367 minutes) Dp (waiting 366 minutes) [04:27:37] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 341 minutes) [04:41:01] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 389 minutes) Saramg (waiting 384 minutes) Joelp (waiting 381 minutes) Dp (waiting 380 minutes) [04:41:02] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 354 minutes) [04:54:26] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 402 minutes) Saramg (waiting 397 minutes) Joelp (waiting 394 minutes) Dp (waiting 393 minutes) [04:54:27] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 368 minutes) [05:07:53] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 416 minutes) Saramg (waiting 411 minutes) Joelp (waiting 408 minutes) Dp (waiting 407 minutes) [05:07:54] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 381 minutes) [05:21:17] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 429 minutes) Saramg (waiting 424 minutes) Joelp (waiting 421 minutes) Dp (waiting 420 minutes) [05:21:18] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 395 minutes) [05:34:38] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 443 minutes) Saramg (waiting 437 minutes) Joelp (waiting 434 minutes) Dp (waiting 433 minutes) [05:34:39] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 408 minutes) [05:48:04] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 456 minutes) Saramg (waiting 451 minutes) Joelp (waiting 448 minutes) Dp (waiting 447 minutes) [05:48:05] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 421 minutes) [06:01:32] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 469 minutes) Saramg (waiting 464 minutes) Joelp (waiting 461 minutes) Dp (waiting 460 minutes) [06:01:33] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 435 minutes) [06:08:16] !log test [06:08:16] Message missing. Nothing logged. [06:08:33] has labs-morebots been stable? [06:08:38] or has it required manual restarts? [06:15:00] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 483 minutes) Saramg (waiting 478 minutes) Joelp (waiting 475 minutes) Dp (waiting 474 minutes) [06:15:01] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 448 minutes) [06:28:20] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 496 minutes) Saramg (waiting 491 minutes) Joelp (waiting 488 minutes) Dp (waiting 487 minutes) [06:28:21] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 462 minutes) [06:41:41] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 510 minutes) Saramg (waiting 505 minutes) Joelp (waiting 501 minutes) Dp (waiting 500 minutes) [06:41:42] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 475 minutes) [06:55:06] Warning: There are 4 users waiting for shell, displaying last 4: Ptarjan (waiting 523 minutes) Saramg (waiting 518 minutes) Joelp (waiting 515 minutes) Dp (waiting 514 minutes) [06:55:07] Warning: There is 1 user waiting for access to tools project: Danilo (waiting 488 minutes) [07:02:37] !tr Danilo [07:02:37] request page: https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/Access_Request/Danilo?action=edit talk page: https://wikitech.wikimedia.org/wiki/User_talk:Danilo?action=edit§ion=new&preload=Template:ToolsGranted link: https://wikitech.wikimedia.org/w/index.php?title=Special:NovaProject&action=addmember&projectname=tools [07:04:01] !log tools petrb: installing maven on -dev [07:04:03] Logged the message, Master [07:08:27] Warning: There are 2 users waiting for shell, displaying last 2: Joelp (waiting 528 minutes) Dp (waiting 527 minutes) [07:43:00] Coren ping [07:50:04] @search gerrit [07:50:05] Results (Found 6): gerrit, whitespace, git-puppet, gerritsearch, ryanland, gitweb, [07:50:14] !git-puppet [07:50:14] git clone ssh://gerrit.wikimedia.org:29418/operations/puppet.git [07:50:21] <3 wm-bot [07:50:40] <3... [08:39:06] !log tools petrb: started toolwatcher [08:39:08] Logged the message, Master [09:00:33] !log tools petrb: removing wd-terminator service [09:00:39] Logged the message, Master [09:02:54] * addshore slaps petan to attention [09:03:01] hey [09:03:05] what's up [09:03:05] pm ;p [09:04:09] petan: thanks a lot. also a full jdk (that contains javac) would be great (in fact needed with maven) [09:05:14] I must fill a separate bug for it? [09:07:51] (also I prefer to use openjdk7 instead but that would not problem) [09:14:18] addshore: pong [09:14:22] ping [09:14:32] addshore: the basic runner for dumpscan is working [09:14:43] check ~/src/python [09:14:49] ~/src/dumpscan/python [09:14:49] even [09:16:30] * addshore goes to look [09:16:32] I get an HTTP 500 for a little php script on tool labs... how can I see the stack trace? [09:17:03] lbenedix: ~/php.err, or something like that [09:17:09] or ~/error.log? [09:17:14] a file in your home folder, anyway [09:17:42] thx [09:18:44] ebraminio hey [09:18:50] ebraminio you don't need to fill in a bug :P [09:18:57] just tell me what you are missing [09:21:18] valhallasw: nice :> [09:21:55] petan: openjdk-7-jdk would be fine! [09:22:09] lbenedix you need to change owner to tool [09:23:01] valhallasw: where is the git repo? :> [09:23:43] petan: what do you mean? [09:24:22] lbenedix that php script [09:24:56] its local-lbenedix:local-lbenedix now [09:25:19] ok, then you should be able to see error in phperror log [09:25:22] in home [09:28:54] !log tools petrb: installed openjdk7 on -dev [09:28:56] Logged the message, Master [09:29:05] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 523800 bytes) [09:29:17] 523800 < 134217728 [09:29:23] lbenedix your script eats too much ram hmm? :P [09:29:31] tried to allocate +523800 [09:29:38] that is not a total memory usage [09:29:46] that is how much it tried to allocate when it got rejected [09:30:00] crazy... [09:30:12] mmmmh [09:30:17] lbenedix even mediawiki works on this configuration and that is memory expensive :P [09:30:49] the script should get an image from a given url and return a dataURI [09:31:16] !log tools petrb: houston we have problem, / on dev is 94% [09:31:18] Logged the message, Master [09:31:55] lbenedix hmm :/ will need to wait for Coren I guess, I don't want to fiddle with php configuration without knowing the details [09:32:13] Okay [09:32:37] why in the ******* is default rootfs 4gb only [09:32:51] * petan slaps Ryan [09:38:04] petan: thanks a lot! works great! :) [09:38:04] next question how to run queries on the database from python code on tool labs? [09:39:51] addshore will tell u :P [09:40:37] * addshore looks? [09:40:58] still xD [09:41:09] I'm not a python person [09:41:18] !log tools petrb: moved /var/log to separate volume on -dev [09:41:20] Logged the message, Master [09:41:29] oh true [09:41:33] damn, that legoktm [09:41:34] :P [09:42:06] lbenedix: MySQLdb [09:42:15] addshore: just local for now [09:42:25] valhallasw: kk :) [09:42:27] addshore: but feel free to add a github remote and push it there [09:42:39] I may do at some point :) [09:43:07] so what script do I need to pass the id number? :) [09:43:14] jobrunner [09:43:23] dumpparser is now used as library [09:43:40] * addshore sees nothing called jobrunner ;p [09:44:12] parserjob [09:44:14] whatever :p [09:44:22] something something job [09:44:42] python parserjob.py 2 ? [09:44:45] basically [09:44:51] * addshore goes to try :D [09:44:54] mehehee [09:44:55] but it doesn't use all json properties yet [09:45:01] kk [09:45:10] just namespace and 'title contains' for now [09:52:04] !log tools petrb: moving /usr to separate volume expect problems :o [09:52:06] Logged the message, Master [09:52:10] petan: can you install nano on tools-dev? :> [09:52:12] !log tools petrb: on -dev [09:52:14] Logged the message, Master [09:52:33] addshore done [09:52:37] cheers [09:54:51] valhallasw: how am I meant to be passing the id? :P [10:05:13] Upon login to tools-login.wmflabs.org I get a "Did you know that you can find a complete development environment on tools-dev server?". Is tools-login the same thing as tools-dev? [10:05:36] no [10:05:40] it's a different server [10:05:51] ssh tools-dev [10:05:58] to get there [10:06:00] ;) [10:12:13] addshore: as command line argument [10:12:28] python parserjob.py 2 [10:12:37] haha, valhallasw just spotted you had job.run() commented out at the bottom xD [10:13:53] title scanning seems to work awesomllyyy! :D [10:32:29] petan: thanks for the sbt work, I marked the bug as resolved-fixed <3 [10:34:15] Hello y'all, I'm experiencing some anomalous behavior connected to: http://en.wikipedia.org/wiki/Template:GL_Photography_reply. It displays fine in the WikEd preview but merely flashes and disappears on actual pages. [10:34:36] Anyone care to speculate? [10:43:38] hi [10:43:45] martijnHH it works only on -dev [10:44:08] Kevjonesin you should ask in #wikipedia-en [10:46:45] valhallasw: https://github.com/addshore/dumpscan :> [10:47:14] valhallasw: :> https://github.com/addshore/dumpscan [10:50:03] oh my client is going so laggy [10:50:59] whats your github username? :> [10:51:04] Was looking for above average tech skillz. #wikipedia-tech offered some insight. [10:51:15] Tanxs anyway. [10:53:55] addshore: valhallasw [10:53:59] big surprise ;-) [10:54:12] :> [10:54:19] awesome, added you to the repo [10:54:25] thx [10:54:29] gonna add some of my thoughts to the issue list ;p [10:54:37] sure [10:57:26] Would y'all be the folks to talk to about automating (scripting?) some of the functions of http://en.wikipedia.org/wiki/Wikipedia:Graphics_Lab/Photography_workshop/Eight_Requests ? [10:58:44] hmm [11:03:01] I'm envisioning crowd sourcing suggestions by having users note image files in need of work on a page with data fields which would feed into a database for a bot to pull from to automatically update the display after automatically archiving "done" requests. [11:04:23] Crowd source rather than pull from categories at random so as to prioritize in use files and avoid files that have already been fixed but still have old maintenace tags. [11:06:13] heh petan you know what I was saying at the hackathon about huggle just dieing? :P [11:06:14] well https://en.wikipedia.org/wiki/Wikipedia:Huggle/Feedback#Huggle_hanging_and_displaying_error_message xD [11:06:25] meh [11:11:08] is huggle on github? [11:11:19] yup [11:11:28] https://github.com/huggle/huggle [11:11:34] thanks [11:12:10] current version is in /huggle I think [11:14:51] the fix is "buy more memory" ;) [11:16:22] HAHA [11:55:14] wow, thats hillarious [11:55:24] ? [11:55:25] huggle just seems to eat and eat and eat memory now xD [11:55:31] wth [11:55:34] it can start with say 250mb [11:55:41] withing 10 seconds be at a 1GB [11:55:46] within 20 be at 2Gb [11:55:50] and then just break everything xD [11:55:53] weird [11:56:06] I think it's related to IE memory leak but howcome it started now? [11:56:13] no idea :P [11:56:22] * addshore digs deeper [12:55:23] petan: still around? [12:55:30] no [12:55:50] :P [12:55:56] any idea what line 57 here is actually setting? https://github.com/huggle/huggle/blob/master/huggle/Misc.vb [12:56:03] GlExcess [12:56:40] just making sure something doesnt loop too much? GlobalLoopExcess? :P [12:57:05] Thats the problem :P [12:59:03] setting it to 10 seems to work quite well [13:06:22] yes [13:06:40] addshore that is a check which prevent some dangerous loops I discovered from looping endlessly [13:06:52] because there are some :P [13:06:54] xD [13:06:56] not that I wrote them [13:07:02] it's original gurch work [13:07:16] Well, they seem to suddely get worse so I'll reduce the limit to 10 and do another release ;p [13:07:32] fixes the memory problem for now :P [13:15:50] addshore ok but keep in mind that reducing these to low values may affect the functionality, so make sure to test if it works [13:16:12] I did :) as far as I can tell the limit is only used on 2 functions in Misc [13:16:30] mhm [13:16:43] you should like keep reverting vandals for at least 30 minutes to be sure :P [13:16:51] I will :p [13:17:15] oh actually its used in 59 loops [13:17:38] I will definatly have to do a bit more tested ;p [13:18:19] OR [13:18:32] you can make a beta release and ping all these people listed as beta testers :D [13:18:36] there is like 40 of them [13:21:36] petan: maybe :P [13:21:48] im gonna see how huggle works with wikidat first ;p [13:59:22] valhalla1w: ty [14:03:37] does the database schema graphic indicate which columns are indexed? [14:14:17] Coren: https://bugzilla.wikimedia.org/show_bug.cgi?id=48910 unauthenticated lists of users? [14:15:18] Ryan_Lane: ... that was confusingly worded. Getting the list of users without privileged credentials is hitting the LDAP search limit is what I meant. Andrew is working on a paged search version that should circumvent. [14:15:34] ah [14:15:41] yeah. we have a shitton of entries now [14:15:52] I had increased the limit fairly high recently too [14:15:58] I have a workaround now by changing the base DN to be project-by-project so that it gets fewer entries, but that just delays the problem. [14:16:04] How recently? [14:16:13] a month or so ago? [14:16:31] Heh. Atm, bare 'ldaplist' hits the limit again. :-) [14:16:35] yep [14:16:49] that's a *lot* of entries [14:17:05] paging solves all :D [14:17:50] we're going to need to switch to the better method of uid/gid generation you suggested soon, too [14:18:31] Well, we're using all-linux, so we *could* switch to 64 bits [ug]ids. :-) [14:18:41] ah. wikitech-interface component. good idea [14:18:52] Warning: There is 1 user waiting for shell: Justincheng12345 (waiting 0 minutes) [14:18:53] ewww [14:19:09] we have a really long time before that's necessary ;) [14:19:28] 32 would be good though. [14:19:54] IIRC, there haven't been issues with 32 bit [ug]ids since 2008 [14:20:06] * Ryan_Lane nods [14:20:24] I'm sure grid engine will find a way! [14:20:26] :) [14:20:56] It's actually fairly simple to test; just need a single user with uid >64k to test it [14:21:33] yep [14:21:52] I think we're pretty far from hitting that uid range, but it's worth testing [14:22:49] so… we really need a generic labs proxy that does https [14:23:27] that can have *.wmflabs.org, *.tools.wmflabs.org and maybe some other certs [14:23:35] well, cert names [14:25:32] because I very badly don't want projects embedding certs [14:26:15] self-service load balancer/proxy creation would be nice to go with it [14:30:10] hi, Ryan_Lane :) what should i do to be able to reach the sql hosts (enwiki.labsdb etc) from the new vm? [14:30:39] JohannesK_WMDE: sudo su - local-catgraph [14:31:22] Ryan_Lane: local-catgraph@sylvester:~$ mysql -h enwiki.labsdb [14:31:23] ERROR 2005 (HY000): Unknown MySQL server host 'enwiki.labsdb' (0) [14:31:39] I think you have to use a different defaults file [14:31:58] -login and -dev have the host names in /etc/hosts. i tried using the ip addresses from there, but 'network is unreachable' [14:32:11] ah. right [14:32:14] Well, tools.wmflabs.org has a cert, but it's a no-enduser box. [14:32:14] Coren: ^^ heh [14:32:22] Warning: There is 1 user waiting for shell: Justincheng12345 (waiting 13 minutes) [14:32:50] Coren: yeah, still not a huge fan of putting the certs there, though. I'd rather have it somewhere that isn't accessible to anyone but ops [14:32:50] JohannesK_WMDE: It's a ugly hack atm. (Ryan_Lane: we need to fix that soon) [14:32:50] yep :) [14:33:03] JohannesK_WMDE: Look on tools at /etc/iptables.conf [14:33:21] ok, will do Coren [14:33:22] Coren: we can put them in LDAP [14:33:23] JohannesK_WMDE: Then shudder in horror. :-) [14:33:29] Ryan_Lane: The certs? [14:33:36] the dns entries ;) [14:34:00] uh. why do you do it this way? :) [14:34:03] it's enwiki.labsdb.pmtpa.wmflabs, right? [14:34:19] JohannesK_WMDE: because they are all on a single host and have different ports [14:34:23] Ryan_Lane: Ah! Didn't you want to wait until we had a cleaner automated way of doing it though? I'm thinking pull from mediawiki-config/*.dblist? [14:34:58] Ryan_Lane: But you said you didn't want a new mechanism to inject names. [14:34:59] hm [14:35:19] well, it depends on whether we want this in production or labs dns [14:35:24] production is likely better [14:35:35] petan: Coren: How can I download the huggle whitelist from inside the labs? [14:35:39] for that we really want to wait till faidon is done with the new DNS server [14:35:46] Is it? By definition the labsdb is... for the labs. :-) [14:36:02] yeah, but the actual servers are in production [14:36:10] a930913: Where does it live? [14:36:10] we have weird splits of services [14:36:37] Coren: heh. I see an issue with the naming convension you chose [14:36:38] Coren: huggle.wmflabs.org [14:36:38] Ryan_Lane: I guess the question is, does production care about the aliases? [14:36:44] convention [14:36:44] Ryan_Lane: What? [14:36:49] mrwiki.labsdb [14:37:02] how to choose between pmtpa and eqiad? [14:37:10] a930913 why would you want to do that? [14:37:17] There is just the one labsdb, isn't it? [14:37:19] a930913 just use huggle-wiki instance [14:37:34] petan: Hmm? [14:37:37] Coren: no. per datacenter [14:37:52] Ryan_Lane: Ah. [14:38:07] Well, that changes nothing then. *.labsdb.* works just as well [14:38:19] *.labsdb.*? [14:38:32] enwiki.labsdb.pmtpa.wmflabs [14:38:36] yeah [14:38:39] that means it needs to be in LDAP [14:38:40] enwiki.labsdb.eqiad.wmflabs [14:38:41] um... to access the replicated dbs, should i just copy /etc/iptables.conf for now, Ryan_Lane? what do you suggest? [14:38:56] yeah. that's likely easiest for now [14:39:01] JohannesK_WMDE: For now, copy the iptables.conf is the easiest thing to do. [14:39:10] ok. thx [14:39:12] we'll be solving all the issues you're running into soon :) [14:39:15] JohannesK_WMDE: Once the "real" system is in place, it just becomes obsolete/ [14:39:24] welcome to being the first to use this stuff outside of tools ;) [14:39:39] hehe ok. :) [14:39:48] horray for guinea pigs! [14:40:18] (I used 192.* on purpose, so that once the "real" IPs are in place, just chaninging name resolution will work) [14:40:30] * Ryan_Lane nods [14:40:48] is it one ip per slice? [14:41:50] * Coren nods. [14:42:16] 192.168.99.n where n is the slice [14:43:16] wtf? http://www.mediawiki.org/wiki/Extension:TwoFactorAuthentication [14:43:25] why was a fork needed? [14:44:41] ugh. and the license was changed to GPL3 or later? [14:44:45] * Ryan_Lane grumbles [14:44:48] what an asshole [14:45:57] Warning: There is 1 user waiting for shell: Justincheng12345 (waiting 27 minutes) [14:52:52] Ryan_Lane what is wrong on GPL3? [14:53:30] petan: nothing, except that OATHAuth is licensed GPL2 or higher [14:53:44] so, unless I change the license to GPL3, I can't take any changes [14:53:57] which makes what he did a totally dick move [14:54:47] is there some other extension with this functionality? [14:55:02] http://www.mediawiki.org/wiki/Extension:TwoFactorAuthentication [14:55:05] aha [14:55:14] I see f Extension:OATHAuth, [14:55:21] mhm he forked it... [14:55:24] lol [14:55:38] forked two months later [14:55:48] he didn't even bother to ask if I'd accept patche [14:55:50] *patches [14:55:55] that's why I hate forking of repositories [14:56:00] Change on 12mediawiki a page Wikimedia Labs was modified, changed by Danilo.mac link https://www.mediawiki.org/w/index.php?diff=705637 edit summary: [+15] +link to [[Wikimedia Labs/Tool Labs]] [14:56:11] it just produces a mess [14:59:02] AT&T is driving me insane this morning :P [14:59:22] I don't know if my earlier message made it through, but it's not really legal for him to relicense gpl-2+ code as gpl-3+, I don't think [14:59:44] well, it's or higher, so I think it is [15:00:16] you could take a gpl-2+ codebase and add some gpl-3+ new code to it [15:00:29] but you can't just change the license on the old code from 2+ to 3+ [15:00:53] and you're getting into really murky waters if the "new code" is in some of the same files as the old code [15:02:05] Change on 12mediawiki a page Wikimedia Labs/Tool Labs was modified, changed by Danilo.mac link https://www.mediawiki.org/w/index.php?diff=705642 edit summary: [+82] [15:02:51] bblack: hm. need a lawyer :) [15:03:31] I was always under the impression that the code could be relicensed higher, but that the old code was still gpl2 [15:04:05] of course now that I said that, I'm not as sure as I was 15 seconds ago [15:04:06] so any modifications afterwards would be gpl3, but previous codebase could be forked as gpl2 or higher [15:04:33] of course, this makes things *really* difficult to deal with [15:05:49] Ryan_Lane: Well, does TwoFactorAuthentication offer something OATHAuth does not? :-) [15:06:14] scfc_de: a couple config options? simplified code? [15:06:16] otherwise it seems not [15:06:19] The only thing I'm fairly certain of: if I publish gpl2+ code, and someone forks it and makes minor modifications, I don't think they can relicense that as 3+ and thus prevent the changes flowing back to my 2+ copy. [15:06:20] what's all murky is if they add a substantial body of new gpl3+ code and have different licenses on those files/chunks than on my original gpl2+ files/chunks, all within one project. [15:06:44] bblack: they can prevent the new changes from being moved back in, can they not? [15:06:49] the licenses are compatible to allow him to mix code like that, and I don't think you could then take his new gpl3+ additions back to your gpl2+ project [15:06:50] unless you want yours to be mixed-license by chunk/file as well [15:07:07] this confusion is one of the reasons I'm pissed off [15:07:11] I don't want to deal with this [15:07:34] Ryan_Lane: at the very least that's completely antithetical to the aims of the GPL in general. But I really don't think you can mod gpl-2+ code and then call the old+mods gpl-3+ only. [15:07:47] * Ryan_Lane nods [15:08:26] but there's a distinction to be drawn between "I made a few minor corrections/additions to the existing body of code" and "I mixed the old code with a separate chunk of brand new code of compatible licensing, into a single project with source files of different compatible licenses" [15:08:35] bblack: To further the aims of the GPL, new versions of the licence are developed. In fact, the FSF pushes GPL 3 quite hard. [15:08:51] yeah [15:09:02] you can of course use GPL-2 without the "or later" clause [15:09:27] But I can't imagine the intent was to let a forker force the original to upgrade his license [15:10:48] hmmm. i installed iptables, copied iptables.conf from tools-dev and ran "iptables-restore < /etc/iptables.conf", but iptables -L still just prints an empty list [15:10:59] The forker doesn't force anyone. Regarding removing "or later", I would ask a lawyer. The GPL is copyrighted. [15:11:12]