[00:04:08] 10Phabricator: Add a blog for internal design research updates in Reading team - https://phabricator.wikimedia.org/T134951#2283566 (10pizzzacat) > No, creating posts in an existing blog and creating blogs should be entirely separate things... And if they're not let's open an upstream bug :) Great. Things don't... [00:06:38] 10Phabricator: Add a blog for internal design research updates in Reading team - https://phabricator.wikimedia.org/T134951#2283584 (10Krenair) We need an admin to be able to do anything [00:10:21] twentyafterfour: D223 has a little bug that I didn't notice on review. If there is no match for the ldapname(s) passed then you get a resultset with 100 random phab accounts [00:10:21] D223: user.ldapquery conduit method for @bd808 - https://phabricator.wikimedia.org/D223 [00:10:46] that happens because $phids stays empty [00:10:51] bd808: oh, right [00:10:58] My bad, easy to fix [00:11:08] cool. [00:14:33] it would be nice if you could figure out how to add the ldap user name to the response records too [00:15:00] I'm not sure if that's easy or not. [00:15:39] as it works now querying for a list of ldap users will give a set of results but there is no way to know which account is which [00:21:08] 10Phabricator, 06Community-Tech-Tool-Labs: LTC needed for user.ldapquery conduit api - https://phabricator.wikimedia.org/T134959#2283616 (10bd808) [00:21:22] 10Phabricator, 06Community-Tech-Tool-Labs: LTC needed for user.ldapquery conduit api - https://phabricator.wikimedia.org/T134959#2283631 (10bd808) [00:21:25] 10Diffusion, 06Community-Tech-Tool-Labs, 06Labs, 10Tool-Labs, 15User-bd808: Create application to manage Diffusion repositories for a Tool Labs project - https://phabricator.wikimedia.org/T133252#2283630 (10bd808) [00:23:54] bd808: D230 [00:23:54] D230: ldapnames must match at least one phid to query users data. - https://phabricator.wikimedia.org/D230 [00:24:26] bd808: adding ldap username to the response will be easy, let me update the diff real quick [00:25:22] 10Phabricator, 06Community-Tech-Tool-Labs: LTC needed for user.ldapquery conduit api - https://phabricator.wikimedia.org/T134959#2283636 (10bd808) [00:30:18] bd808: done [00:31:10] 10Phabricator, 06Community-Tech-Tool-Labs: LTC needed for user.ldapquery conduit api - https://phabricator.wikimedia.org/T134959#2283641 (10mmodell) D230 should be good to go now. [00:34:18] twentyafterfour: I still don't have a testing phab system, but the logic looks good [00:35:22] bd808: cool, I can deploy it and test it live I guess :) [00:35:44] nothing quite as awesome as hot patches [00:36:56] I spent an hour today trying to remember how I created a certificate to talking to the phab api before I figured out that those are old news and tokens work so much better now. [00:37:30] I kept trying to figure out how to turn a token into a certificate [00:41:44] bd808: deployed it .. [00:41:55] such service! [00:42:05] :) [00:42:22] yeah the tokens vs certificates thing is annoying, they haven't really documented the change much at all [00:42:27] "APIError: Unknown or missing ldap names: bd808notreally (ERR-INVALID-PARAMETER)" bam! [00:42:45] the new token stuff is much easier to use [00:43:03] yeah but confusingly a lot of things refer to the old way of doing it [00:43:09] I finally tracked this down -- https://github.com/disqus/python-phabricator/pull/23/files [00:43:17] and that made it all clear [00:43:45] heheh, I had to make the same change by taking stabs in the dark (I didn't find that pull...sadly) [00:44:21] I need to go fix stashbot to use a token instead of a cert which will also kill off a bug with sessions going stale [00:47:22] so I tried user.ldapquery with ["bd808", "20after4"] and I didn't get a result for bd808. I don't know if that's an error in the code or you don't have ldap name registered ;) [00:47:42] My ldap name would be BryanDavis [00:48:00] ah there we go [00:48:04] cool it works... [00:48:38] would you prefer the structure was indexed on ldap_username instead of numeric indexes? [00:49:21] numeric is fine I think [00:49:31] ok cool. [01:01:08] 10Diffusion, 06Community-Tech-Tool-Labs, 06Labs, 10Tool-Labs, 15User-bd808: Create application to manage Diffusion repositories for a Tool Labs project - https://phabricator.wikimedia.org/T133252#2283658 (10bd808) [01:01:10] 10Phabricator, 06Community-Tech-Tool-Labs: LTC needed for user.ldapquery conduit api - https://phabricator.wikimedia.org/T134959#2283656 (10bd808) 05Open>03Resolved Thanks for the quick fix @mmodell! [01:01:51] Tomorrow I start figuring out the new repo creation api [12:54:42] 10Phabricator: Herald rule for "Expiring watchlist entries" - https://phabricator.wikimedia.org/T134985#2284880 (10Tobi_WMDE_SW) [13:02:17] 10Phabricator: Herald rule for "Expiring watchlist entries" - https://phabricator.wikimedia.org/T134985#2284909 (10Aklapper) 05Open>03Resolved a:03Aklapper I added that project to H31 which was created in T100640. [17:43:10] 10Phabricator: Conpherence takes too mush screen space - https://phabricator.wikimedia.org/T135024#2286043 (10MaxSem) [17:44:04] 10Phabricator: Conpherence takes too much screen space - https://phabricator.wikimedia.org/T135024#2286068 (10MaxSem) [17:47:09] 10Phabricator: Conpherence takes too much screen space - https://phabricator.wikimedia.org/T135024#2286043 (10greg) Where? [17:49:37] greg-g: Yeah I was about to ask for a screenshot. [17:51:36] you can open maniphest as a tab that is visible in all other pages [17:51:42] eh, conpherence [17:51:57] but I can't figure out how to enable it again [17:52:30] Oh yeah I remember that before, but I don't remember how to turn it on [17:53:00] https://www.mediawiki.org/wiki/Phabricator/Help#Using_Conpherence [17:53:02] and "no way to hide this feature", heh, such confusion :) [17:53:04] 10Phabricator: Conpherence takes too much screen space - https://phabricator.wikimedia.org/T135024#2286111 (10Aklapper) Thanks for reporting this. Please provide steps to reproduce the problem. (Or a screenshot that does not expose confidential information.) Also see https://www.mediawiki.org/wiki/How_to_report_... [17:53:57] 10Phabricator: Conpherence takes too much screen space - https://phabricator.wikimedia.org/T135024#2286043 (10valhallasw) You can hide the column by pressing `\`, or by clicking the menu (hamburger) icon and selecting 'hide column'. [17:54:58] 10Phabricator: Conpherence takes too much screen space - https://phabricator.wikimedia.org/T135024#2286119 (10MaxSem) {F3996305} 13", 100% zoom [17:55:29] 10Phabricator: Add a blog for internal design research updates in Reading team - https://phabricator.wikimedia.org/T134951#2286121 (10pizzzacat) Who is the admin? [17:56:01] 10Phabricator: Conpherence takes too much screen space - https://phabricator.wikimedia.org/T135024#2286137 (10MaxSem) Hamburger menu where? [17:56:02] ahhhh, the menu icon doesn't show up if you're not in any channels [17:56:39] 10Phabricator: Conpherence takes too much screen space - https://phabricator.wikimedia.org/T135024#2286138 (10Aklapper) Screenshot looks legit. I wouldn't say it takes too much space for a side bar. (But I still wonder if it's known that you can hide that Conpherence panel.) [17:56:43] Meouw. [17:59:09] 10Phabricator: Conpherence takes too much screen space - https://phabricator.wikimedia.org/T135024#2286141 (10valhallasw) The menu apparently only appears if you have used Conpherence to send/receive messages: {F3996324} [17:59:19] 10Phabricator: Conpherence takes too much screen space - https://phabricator.wikimedia.org/T135024#2286142 (10greg) 1. Neat! I never saw that feature before (quick access to conpherence rooms via `\` 2. It is a bug that the menu bar isn't visible when you aren't in any rooms [18:00:48] 10Phabricator: Conpherence takes too much screen space - https://phabricator.wikimedia.org/T135024#2286152 (10greg) So, this task is now complicated. It's either: 1. The (should be easily enabled/disabled) conpherence sidebar is too large no matter what or 2. The users thought that sidebar was now standard and w... [18:08:41] 10Phabricator: Add a blog for internal design research updates in Reading team - https://phabricator.wikimedia.org/T134951#2286172 (10Krenair) The list of admins is available at https://phabricator.wikimedia.org/people/query/zYtnRSCkBXQ./ people with operations access on the servers have access to the generic @a... [18:32:09] mutante: https://phabricator.wikimedia.org/D231 [19:33:09] 10Phabricator, 06Operations, 10Traffic: Phabricator needs to expose notification daemon (websocket) - https://phabricator.wikimedia.org/T112765#2286465 (10chasemp) [20:27:50] 10Phabricator, 06Operations, 10Traffic: Phabricator needs to expose notification daemon (websocket) - https://phabricator.wikimedia.org/T112765#2286694 (10Dzahn) So then same hostname but different port. [20:36:50] 10Phabricator: Add a blog for internal design research updates in Reading team - https://phabricator.wikimedia.org/T134951#2286749 (10pizzzacat) Ok, so I guess the question I have been trying this whole time to ask is, which actual person do I need to contact for "things like this"? Thank you for your help! [20:37:25] 10Phabricator: Add a blog for internal design research updates in Reading team - https://phabricator.wikimedia.org/T134951#2286751 (10Krenair) The phabricator admins... You do not contact a specific individual. [20:53:10] 10Phabricator: Add a blog for internal design research updates in Reading team - https://phabricator.wikimedia.org/T134951#2286831 (10pizzzacat) gotcha. thanks! [21:01:14] 10Phabricator, 10Phabricator-Upstream: MySQL search only finds whole-word exact matches - https://phabricator.wikimedia.org/T94338#2286868 (10mmodell) [21:27:14] 10Phabricator, 05Release, 07WorkType-Maintenance: Next Phabricator Update - 2016-05-18 - https://phabricator.wikimedia.org/T134443#2287152 (10mmodell) [21:36:47] 10Phabricator: Add a blog for internal design research updates in Reading team - https://phabricator.wikimedia.org/T134951#2283361 (10ori) I created the blog: https://phabricator.wikimedia.org/phame/blog/view/6/ But @pizzzacat is not able to post. Perhaps this requires the creation of an `acl*' group, in which... [21:42:19] 10Phabricator, 06Operations, 10Traffic: Phabricator needs to expose notification daemon (websocket) - https://phabricator.wikimedia.org/T112765#2287225 (10mmodell) @dzahn yes I believe so, port `22280` by default. See [[ https://secure.phabricator.com/book/phabricator/article/notifications/#terminating-ssl-... [21:46:42] 10Phabricator, 05Release, 07WorkType-Maintenance: Future Phabricator Update - https://phabricator.wikimedia.org/T135068#2287234 (10Luke081515) [21:47:02] 10Phabricator, 05Release, 07WorkType-Maintenance: Next Phabricator Update - 2016-05-18 - https://phabricator.wikimedia.org/T134443#2265770 (10Luke081515) [21:47:47] 10Phabricator, 05Release, 07WorkType-Maintenance: Future Phabricator Update - https://phabricator.wikimedia.org/T135068#2287234 (10Luke081515) p:05Triage>03Normal a:03mmodell [21:57:14] 10Phabricator, 05Release, 07WorkType-Maintenance: Future Phabricator Update - https://phabricator.wikimedia.org/T135068#2287312 (10mmodell) @luke081515: thanks :) [22:27:42] 10Phabricator, 05Release, 07WorkType-Maintenance: Future Phabricator Update - https://phabricator.wikimedia.org/T135068#2287474 (10mmodell) [22:27:55] 10Phabricator: Add a blog for internal design research updates in Reading team - https://phabricator.wikimedia.org/T134951#2287478 (10Krenair) That blog's edit policy allows members of a publicly-joinable project access [23:14:14] 10Phabricator: Change/delete username in Phabricator - https://phabricator.wikimedia.org/T133002#2287650 (10mmodell) The only way to unlink it from one wiki account is if you have your account linked to some other authentication method, e.g. ldap. [23:22:35] 10Phabricator: Change/delete username in Phabricator - https://phabricator.wikimedia.org/T133002#2287662 (10mmodell) ==== Request for Clarification: @UY_Scuti: Can you still access the @JAaron95 account? Unlinking the account would be an easy solution if you also had ldap linked, but without an ldap account phab...