[07:23:37] 6Phabricator, 5Patch-For-Review: Make the phabricator OAuth login UI more prominent - https://phabricator.wikimedia.org/T963#1741365 (10Dreamyshade) I personally found this login page confusing today - I totally typed my Wikipedia username & password into the LDAP fields and was confused about why it didn't wo... [08:32:05] 6Phabricator: Circular dependency kills "Add blocking task" dialog - https://phabricator.wikimedia.org/T116141#1741607 (10awight) 3NEW [08:41:50] 6Phabricator: Circular dependency kills "Add blocking task" dialog - https://phabricator.wikimedia.org/T116141#1741628 (10Aklapper) Confirming on Firefox 41. Open "Blocked By" dialog, paste T34482 in the text field, click "Select" once it is shown, click "Save 'Blocked By' Tasks" at the bottom. Browser sends a... [09:02:51] 6Phabricator, 7Regression: Phabricator login page does not show Welcome text / "Click button below" text anymore - https://phabricator.wikimedia.org/T116142#1741641 (10Aklapper) 3NEW [09:03:35] 6Phabricator, 5Patch-For-Review: Make the phabricator OAuth login UI more prominent - https://phabricator.wikimedia.org/T963#16530 (10Aklapper) @Dreamyshade: Thank you a lot for your comment! It made me realize that our login page has regressed. :( I filed {T116142} about that. [09:27:40] 6Phabricator, 7Regression: Phabricator login page does not show Welcome text / "Click button below" text anymore - https://phabricator.wikimedia.org/T116142#1741690 (10Aklapper) This regressed due to https://secure.phabricator.com/T9346 [17:56:38] twentyafterfour: our backup tar has grown 40% in 3 months man, wow [17:56:58] the db backup? [17:58:10] just did a dump w/ gzip befoer I do some project maint [17:58:17] there is one from july [17:58:35] 5.9G->11G (now) [17:59:12] I suspect that there are new things that phabricator is doing to use extra space, but I think phabricator use has gone up as well. Teams are migrating more and more to phabricator, and we've added more repositories over time. The repositories are constantly growing, some of them fairly rapidly. [17:59:25] 11G doesn't seem that large actually, I'm not too surprised [17:59:36] no it's not crazy (compressed) but the rate of growth [17:59:43] but yeah [18:00:07] I think people are also becoming more comfortable splitting up tasks, and commenting liberally on tasks as a way to communicate [18:00:26] I have also seen a few more image attachments recently [18:00:57] I would expect the rate of growth to eventually taper off a bit. I think the image attachments are a big one - we should seriously look at moving file storage out of mysql [18:01:59] meeple27: agreed [18:02:09] and yeah we are going ot be forced to look at an s3 like thing before too long [18:02:22] maybe anotehr year? idk all guess [18:04:10] I think we should be looking into it much sooner than 1 year, because it's going to take time to implement and it'd be better to do it when we aren't running up against major problems [18:04:47] truly [18:07:46] 6Project-Creators, 10Phabricator-Upstream, 15User-Bd808-Test: Per-user projects for personal work in progress tracking - https://phabricator.wikimedia.org/T555#1743134 (10JAufrecht) [18:25:26] Hi - the issue of personal Phabricator task boards came up in TPG triage [18:26:25] We found T555 about piloting this [18:27:15] but it looks like the task stalled out in early 2015 with people expressing interest but no clear next steps to ... make a policy? make a decision? [18:27:18] a few ppl have them, upstream is not excited about it, if it's fairly low traffic there isn't a big issue [18:27:30] we can't handle the namespace challenge of all users doing it [18:27:39] what breaks? [18:28:16] organizational sanity [18:28:27] it's possible we could hack in an exclusion for type ahead or something [18:28:38] but it's a pretty low priority thing due to few use cases [18:29:10] 6Phabricator, 6Project-Creators, 6operations: create acl*operationsteam & acl*procurement projects, cease using #operations for access control - https://phabricator.wikimedia.org/T114135#1743217 (10RobH) Post migration sync up (@chasemp and I have been cleanging things up). Included in migration was also t... [18:29:29] would it be fair to say, blocked by a mix of technical and procedural limitations in Phabricator? [18:29:35] twentyafterfour: what do you think about excluding "credit card" projects from type head to allow personal workboards w/o namespace pollution? [18:30:06] the specific functionality that this breaks is project name completion in input boxes? [18:30:45] it's not sane to make thousands of credit card projects for all users with how we use it no [18:30:57] there is not mechanism for this, we let a few go as it's no big deal [18:30:59] it doesn't scale [18:31:26] so if you are asking if you can do it, sure idc, if you are saying we shoudl do it as a part of process [18:31:32] that's another story [18:32:29] so what's our policy on new accounts? There's a handful of outstanding requests, afaikt. Options: 1) nobody gets new accounts, since there's no clear limit. [18:32:40] 2) set an arbitrary limit and allow the next N requests [18:32:51] 3) make it more important. [18:32:57] there isn't one really [18:32:59] Is "credit card" project a funny name for a private project? [18:33:05] yes :) [18:33:07] I'm recommending 1 or 2, depending on your technical opinion of the risk of 23 [18:33:08] that's the symbol [18:33:11] I mean, the risk of #2. [18:33:32] no one is looking at this at all and the ones in use idk if they are active [18:33:47] it's a very small issue atm [18:35:06] chasemp, why is H86 adding acl*operations-team? [18:35:25] we are opening the #operations project and this is an artifact [18:35:30] should be fixed afaik now [18:35:31] approach 2a) allow everyone who's asked, and if a flood more people ask, then pick a limit. [18:35:45] 2a is fine w/ me assumign it's like ...a dozen people or something [18:38:57] looks like less than that in the thread, plus me. Work is to create project for each, and I think assign it to them and maybe make it private as well? Who should I assign T555 to? [18:39:23] I'm documenting issues that we've thought of/heard of for this, and would be happy to coordinate followup with everybody who wants to use one. [18:39:50] so there is no problem with people creating a dozen new private projects (for personal use)? [18:40:00] dozen people, one each [18:40:20] idk about it at all, but it shoudl still follow the process I imagine, I doubt andre will care [18:42:20] what process? [18:42:44] https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects [18:49:41] eh, hi,i have a tickets assigned to me a with a certain project tag, but that tag got deleted it seems [18:49:46] if i click on it i get a 404 [18:49:56] can i have a tag back for these, whatever the name is [18:50:05] https://phabricator.wikimedia.org/tag/labs-project-wikistats/ [18:51:03] i don't care if it starts with "labs" or not or whatever the name is, just that they don't have anything now [18:51:38] can you give an example of a ticket? [18:51:57] Krenair: https://phabricator.wikimedia.org/T38291 [18:52:33] Actually I can reproduce the error without that, using the search function [18:52:33] ok [18:52:33] https://phabricator.wikimedia.org/T110391 [18:52:40] do we know the new name? [18:53:11] i don't [18:53:19] i assume somebody thought it was "Analytics-Wikistats" [18:53:20] https://phabricator.wikimedia.org/tag/wikistats/ [18:53:21] but it's not [18:53:23] heh [18:53:26] I can probably find it, one sec [18:53:32] I just typed that in... [18:54:12] ah [18:54:30] Aklapper changed project hashtags, added Wikimedia-Labs-wikistats, wikistats; removed labs-project-wikistats. [18:54:35] mutante: ^^ blame andre__ :) [18:54:38] blllame [18:54:41] yeah [18:54:47] so when you chane name it carries over the old name as a hashtag [18:54:51] he removed it? [18:55:00] I don't get it [18:55:05] This has the primary tag labs-project-wikistats [18:55:06] JohnLewis added a hashtag: labs-project-wikistats. [18:55:10] Yet https://phabricator.wikimedia.org/tag/labs-project-wikistats/ is broken [18:55:18] https://phabricator.wikimedia.org/project/profile/543/ works [18:55:18] tht link works for me :) [18:55:20] so i should use "Wikimedia-Labs-wikistats" now? [18:55:28] Or https://phabricator.wikimedia.org/project/board/543/ if you're a fan of the workboard default view [18:55:28] both links work for me Krenair [18:55:33] and just manually fix it? not a big deal [18:55:44] chasemp: I added it as a hashtag just now so maybe why it does :) [18:55:49] I saw this once before when a project was renamed [18:55:56] okay so JohnFLewis just fixed it [18:55:56] before the old hashtag add behavior was default [18:55:57] or soemthing [18:56:01] it created an odd situation [18:56:09] chasemp: yeah, that likely. [18:56:11] somehow [18:56:12] and I fixed it this way then :) [18:56:32] Nemo renamed it away from labs* to wikimedia* and then andre__ renamed it back [18:56:41] ah [18:56:47] no clue how the rename wars pan out [18:57:01] 'rename wars' sounds promising [18:57:28] rename temporary authorization of force? [18:57:28] reminds me i wante to rename in gerrit, heh [18:57:54] which will mean wikitech and icinga and stuff [18:57:56] mutante: we can rename war you there too [18:58:02] hah, right [18:58:06] yes [18:59:20] eh, it seems if i just re-add the same project tag [18:59:22] and save [18:59:29] that fixes it [18:59:56] or because John added the hashtag? [19:08:17] 6Phabricator, 6Project-Creators, 6operations: create acl*operationsteam & acl*procurement projects, cease using #operations for access control - https://phabricator.wikimedia.org/T114135#1743376 (10RobH) So @chasemp created the associated project (new #operations) as the old one was renamed to #acl*operation... [19:08:23] 6Phabricator, 6Project-Creators, 6operations: Create policy projects and convert people projects to open - https://phabricator.wikimedia.org/T90491#1743379 (10RobH) [19:09:07] 6Phabricator, 6operations: unable to subscribe to operations tag after migration and merge from ops-core and ops-request - https://phabricator.wikimedia.org/T89053#1743382 (10RobH) 5Open>3Resolved a:3RobH So with the details listed in T114135, #operations is now joinable by anyone who wants to join. #ac... [19:10:25] 6Phabricator, 6operations: unable to subscribe to operations tag after migration and merge from ops-core and ops-request - https://phabricator.wikimedia.org/T89053#1743395 (10RobH) I noticed after my update there are long standing discussions about policy involving project creation, however it seems outside of... [19:10:40] 6Phabricator, 6Project-Creators, 6operations: create acl*operationsteam & acl*procurement projects, cease using #operations for access control - https://phabricator.wikimedia.org/T114135#1743399 (10chasemp) Outcome: * This mucked up the existing work board for #operations but since we don’t use it we decide... [19:11:52] 6Phabricator, 6operations: Moving procurement from RT to Phabricator - https://phabricator.wikimedia.org/T93760#1743410 (10RobH) As all the ACL groups have been completed, the next step is to simply start testing regular use. (We've done our initial task creation and attachment tests, as well as emailing in t... [19:29:42] 6Project-Creators, 10Phabricator-Upstream, 15User-Bd808-Test: Per-user projects for personal work in progress tracking - https://phabricator.wikimedia.org/T555#1743489 (10JAufrecht) Summarizing discussion on IRC and other places: # There are technical barriers to having a large numbers (100s or 1000s) of p... [19:42:32] 6Project-Creators: Create new project User-JAufrecht - https://phabricator.wikimedia.org/T116218#1743539 (10JAufrecht) 3NEW [20:01:35] 6Phabricator: Visibility of files should be public by default - https://phabricator.wikimedia.org/T115848#1743619 (10Negative24) @mmodell: Glaisher, Aklapper, and me all saw that unlinked files were private, owner-only protected (could this be a bug?) Also, files that were linked to a private task would inherit... [20:08:52] 6Phabricator, 6operations, 7audits-data-retention: Enable mod_remoteip on Phabricator and ensure logs follow retention guidelines - https://phabricator.wikimedia.org/T114014#1743641 (10chasemp) https://secure.phabricator.com/D14315 [20:33:26] 6Project-Creators: Clarify #Phabricator project confusion - https://phabricator.wikimedia.org/T112040#1743786 (10greg) I say we should follow the steps that @chasemp and @robh took for operations: https://phabricator.wikimedia.org/T114135#1743376 See also: https://phabricator.wikimedia.org/diffusion/PHTO/browse... [21:07:00] what's the recommended way of running phpunit tests under vagrant? [21:07:38] brion: i dunno if its recommended, but i use: php tests/phpunit/phpunit.php path/to/tests/i/want/to/run [21:07:47] from mediawiki-core root, even for running extension tests [21:07:56] ebernhardson: well that explodes because i'm the wrong user [21:08:07] so tests see to have problems saving lock files [21:08:18] and 'mwscript tests/phpunit/phpunit.php' seems to get confused [21:08:30] oh, hmm interesting. i guess i havn't run core tests before, just extensions and didn't have that problem [21:08:44] can't su to www-data [21:08:46] maybe mwscript ../tests/phpunit/phpunit.php ? [21:08:58] i know in prod you can .., although usually shouldnt... [21:09:20] (but i've never tried for tests) [21:09:31] The MediaWiki script file "/../tests/phpunit/phpunit.php" does not exist. [21:09:33] ;_; [21:09:45] dunno where the initial / came from [21:09:52] :S [21:11:06] here we are [21:11:07] sudo -u www-data -- php5 tests/phpunit/phpunit.php extensions/TimedMediaHandler/tests/phpunit/TestVideoTranscode.php [22:49:20] brion: mw:MediaWiki-Vagrant kind-of mentioned that command line. I made it more prominent, https://www.mediawiki.org/wiki/MediaWiki-Vagrant#Running_and_debugging_unit_tests . Does a plain `php5 phunit.php` ever work? [22:50:16] spagewmf: should work, depending on the tests... but best to run as the proper user for consistency [22:52:02] for File-related tests i needed the lock files in temp dirs to work as expected [23:14:03] brion: thanks, the page now gives just one way to run phpunit. [23:14:28] Woot! [23:14:33] Many tanks [23:30:07] chasemp: I could probably hack in an exclusion [23:40:12] 6Phabricator: Visibility of files should be public by default - https://phabricator.wikimedia.org/T115848#1744378 (10mmodell) Drag and drop uploads use a more restrictive policy. If other uploads are also using a restrictive policy then that is an issue. See [[ https://secure.phabricator.com/diffusion/P/browse/m... [23:45:34] 6Phabricator: Visibility of files should be public by default - https://phabricator.wikimedia.org/T115848#1744404 (10mmodell) Here's a non-drag-and-drop upload: {F2752490} It used "public" as the default policy. When uploading directly into a text field, the file assumes the policy of the object it's attached... [23:48:24] 6Phabricator, 6operations, 7audits-data-retention: Enable mod_remoteip on Phabricator and ensure logs follow retention guidelines - https://phabricator.wikimedia.org/T114014#1744423 (10mmodell) There are now retention policy options that we can configure in the phabricator garbage collectors: https://phabri...