[07:44:58] 3Phabricator.org: Image viewer footer is not correctly anchored, obscures lowest part of the image - https://phabricator.wikimedia.org/T78075#939265 (10Qgil) Can you test this problem in Chrome Canary (v41) Mac, please? See https://secure.phabricator.com/T6794#88229 [07:45:13] 3Phabricator.org: image viewer close button moves with view scroll - https://phabricator.wikimedia.org/T78077#939266 (10Qgil) Can you test this problem in Chrome Canary (v41) Mac, please? See https://secure.phabricator.com/T6794#88229 [07:52:51] 3Phabricator, § Phabricator-Sprint-Extension: Create a continuous integration plan for the Sprint extension - https://phabricator.wikimedia.org/T85123#939268 (10Christopher) 3NEW [07:56:18] 3Language-Engineering, Project-Management: Migration of Language team to Phabricator - https://phabricator.wikimedia.org/T829#939281 (10Qgil) a:3Arrbee Runa, in practice you are the Language team member coordinating the migration. Let me assign this task to you. How is you first sprint with Phabricator going?... [07:56:34] 3Phabricator, § Phabricator-Sprint-Extension: https://phabricator.wikimedia.org/tag/XXX/board/ times out - https://phabricator.wikimedia.org/T78208#939284 (10Christopher) @Qgil please check T85123 and we can work out this slow review and merge situation there. [08:08:30] 3Phabricator, Phabricator.org: We need a Wikimedia process for filing tasks and patches upstream in the name of Wikimedia - https://phabricator.wikimedia.org/T1298#939296 (10Qgil) Column renamed to "Upstreamed". I agree the title is clearer now, and I hope the sequence of columns makes also clear that "Wikimedia... [08:22:30] 3Phabricator, § Phabricator-Sprint-Extension: Create a continuous integration plan for the Sprint extension - https://phabricator.wikimedia.org/T85123#939300 (10Qgil) While I agree that we need to find a way to integrate Sprint releases sooner and faster, it is good to take into account that last week we had the... [08:22:39] 3Phabricator, § Phabricator-Sprint-Extension: Create a continuous integration plan for the Sprint extension - https://phabricator.wikimedia.org/T85123#939306 (10Qgil) p:5Triage>3Normal [08:56:02] 3Phabricator: Add optional "contact user" link to Phabricator user profiles - https://phabricator.wikimedia.org/T78238#939333 (10Qgil) Maybe it's not a valid comparison, but we are not going to scan users' private communications in any case. In order to construct a useful link like https://www.mediawiki.org/w/i... [08:57:20] 3Phabricator: Add optional "contact user" link to Phabricator user profiles - https://phabricator.wikimedia.org/T78238#939334 (10Qgil) [08:59:17] 3RT-Migration, operations: Migrate access-requests@ from RT to Phabricator - https://phabricator.wikimedia.org/T84861#939335 (10Qgil) [09:07:45] 3Phabricator: Upgrade phab-01 to use the same version as production Phabricator - https://phabricator.wikimedia.org/T78168#939340 (10Qgil) How complex is to update phab-01 at the same time than phabricator.w.o? In the past weeks we have seen several problems in production that perhaps could ave been avoided wit... [09:11:46] 3Phabricator: Upgrade phab-01 to use the same version as production Phabricator - https://phabricator.wikimedia.org/T78168#939343 (10yuvipanda) @qgil as I mentioned in an earlier comment, I actually have no idea how this works - when I initially set it up I just followed @chasemp's documentation. [09:20:55] 3Phabricator: Actions shouldn't be attributed to bzimport - https://phabricator.wikimedia.org/T847#939347 (10Qgil) > I must be able to search reports according to their reporter whatever the fate of the reporter was Imagine that you need to search all the tasks authored by DanClemmensen, a user that (as of toda... [09:23:45] 3Phabricator.org: Add IRC name and MediaWiki Username as alternate auto-complete lookups - https://phabricator.wikimedia.org/T877#939351 (10Qgil) [09:26:47] 3Phabricator.org: 503 when batch-editing tasks in Phab - https://phabricator.wikimedia.org/T76152#939352 (10Qgil) [09:27:14] 3Phabricator.org: 503 when batch-editing tasks in Phab - https://phabricator.wikimedia.org/T76152#791472 (10Qgil) @Quiddity also reported a timeout after 100 tasks. [09:37:52] 3Phabricator, Code-Review, Wikimedia-Git-or-Gerrit: gerritbot should report both author and committer - https://phabricator.wikimedia.org/T76291#939374 (10Qgil) p:5Low>3Volunteer? This has been the status quo for a long time. It doesn't really matter who uploaded/created the patch, the call for action is tha... [09:40:48] 3Phabricator: Sending email to create tasks doesn't work for me - https://phabricator.wikimedia.org/T1077#939382 (10Qgil) @MarkAHershberger can you test against http://secure.phabricator.org , please? For instance, trying to create this very same task there. This way we will know whether this is a Phabricator p... [09:41:39] 3Phabricator.org: Allow group members to be managed by external service (i.e. ldap) - https://phabricator.wikimedia.org/T550#939389 (10Qgil) [09:42:06] 3Phabricator.org: There should be a better way of communicating the message about exceeding size limit while uploading file in Phabricator - https://phabricator.wikimedia.org/T159#939390 (10Qgil) [09:42:34] 3Phabricator: enotifs are sent from no-reply@phabricator.wikimedia.org - https://phabricator.wikimedia.org/T85127#939391 (10Glaisher) [09:45:26] 3Phabricator: Phabricator project display names use awkward capitalization and hyphenation - https://phabricator.wikimedia.org/T911#939401 (10Qgil) [09:48:31] 3Phabricator, Phabricator.org: Profiles of users with private tasks time out when accessed by users without permissions to see them - https://phabricator.wikimedia.org/T85046#939404 (10Qgil) [09:49:21] 3Phabricator: High level overview of Phabricator projects - https://phabricator.wikimedia.org/T833#939406 (10Qgil) [09:52:20] 3Phabricator, Phabricator.org: enotifs are sent from no-reply@phabricator.wikimedia.org - https://phabricator.wikimedia.org/T85127#939409 (10Qgil) p:5Triage>3Low [09:53:38] 3Phabricator, Phabricator.org: enotifs are sent from no-reply@phabricator.wikimedia.org - https://phabricator.wikimedia.org/T85127#939391 (10Qgil) Good catch! Upstream also uses noreply@. notification@? [09:55:10] 3Phabricator.org: Phabricator is unfriendly to assistive technology - https://phabricator.wikimedia.org/T109#939418 (10Qgil) [09:56:30] 3Phabricator, Phabricator.org: enotifs are sent from no-reply@phabricator.wikimedia.org - https://phabricator.wikimedia.org/T85127#939420 (10Glaisher) BTW, does the reply with email thing work? I haven't tried it yet. [10:00:38] 3Phabricator, Phabricator.org: enotifs are sent from no-reply@phabricator.wikimedia.org - https://phabricator.wikimedia.org/T85127#939430 (10valhallasw) Some people have reported issues, but I think it's working overall. As for the //address//, I think this is a local configuration choice (we're using no-reply@... [10:02:55] 3Phabricator, Phabricator.org: enotifs are sent from no-reply@phabricator.wikimedia.org - https://phabricator.wikimedia.org/T85127#939436 (10Glaisher) The Reply-To: header points you to a unique specific address [10:36:56] 3Collaboration-Team, Project-Management: Trello migration script - https://phabricator.wikimedia.org/T821#939498 (10Qgil) Attachments and comments are clear requirements for a migration script, yes. About checklists, what Phabricator can offer is described in T1141. Have you decided which route is best to take... [11:02:11] 3Phabricator: Reporters of imported reports should receive notifications for them - https://phabricator.wikimedia.org/T896#939523 (10Qgil) It is also worth noting that users that have no access to their old email addresses will not be able to claim their Bugzilla activity. See for instance T54385. However, the... [11:20:55] Hi [11:21:27] Does anyone know how long Bugzilla needs to be open/available in the form of Bugzilla? [11:29:02] JohnFLewis: as far as I know, the plan is to keep old-bugzilla for the forseeable future [11:30:26] The plan is to move bugs-attachment to behind varnish but even better would be to get rid of it but it holds the attachments for BZ so :/ [11:32:59] i think what he wants is a more specific "forseeable future" [11:33:20] because ..cert issues etc [11:33:42] Indeed. I assume andre__ and qgil will give better answers when the American office hours roll around [11:33:48] JohnFLewis: i once suggested to make a static Bugzilla [11:34:04] bugzilla-static as opposed to old-bugzilla [11:34:13] which would just be static HTML [11:34:27] no logins, no saved searches, no Perl cgi at all [11:34:32] just the content of all bus [11:34:34] bugs [11:34:45] ahh [11:34:54] that also means we dont have to maintain the actual BZ application [11:35:27] see this https://phabricator.wikimedia.org/T1198 [11:35:42] mutante: but what is the point of maintaining the content at all? [11:37:44] maybe this https://phabricator.wikimedia.org/T78747 [11:57:29] 3Phabricator, Phabricator.org: enotifs are sent from no-reply@phabricator.wikimedia.org - https://phabricator.wikimedia.org/T85127#939553 (10Aklapper) p:5Low>3Volunteer? Which real problem exists here? Only that reading "no-reply@" might make you think that you cannot reply via email, or something more? I'd... [12:00:17] 3Phabricator, Phabricator.org: enotifs are sent from no-reply@phabricator.wikimedia.org - https://phabricator.wikimedia.org/T85127#939561 (10Dzahn) I think it's a valid bug that it's no-reply when there is a _reply_ handler. Mail filter are still young but we will use this hopefully for years. [12:03:04] any reason that "find ways to import RT tickets into phabricator" is still open? [12:04:32] 3RT-Migration, operations: Migrate RT to Phabricator - https://phabricator.wikimedia.org/T38#939565 (10Dzahn) "update docs" is the last open subtask? call this resolved yet? [12:05:23] 3Phabricator, Phabricator.org: enotifs are sent from no-reply@phabricator.wikimedia.org - https://phabricator.wikimedia.org/T85127#939578 (10Dzahn) we need to check if the reply handler really works at T1077 [12:08:29] 3Language-Engineering, Project-Management: Migration of Language team to Phabricator - https://phabricator.wikimedia.org/T829#939585 (10Arrbee) Hi @Qgil, we are already on the 2nd sprint and about to start the 3rd sprint on phabricator tomorrow. Till now, it has been very convenient to create tasks. An important... [12:10:14] 3Phabricator.org: 503 when batch-editing tasks in Phab - https://phabricator.wikimedia.org/T76152#939587 (10Aklapper) > Looks like it kills itself pretty exactly after 100 tasks. Might be coincidence. Actually the number 100 here is coincidence, it's probably based on a certain timeframe instead. I'm not convin... [12:48:47] 3Phabricator, Analytics-Tech-community-metrics, Engineering-Community: Monthly report of total / active Phabricator users - https://phabricator.wikimedia.org/T1003#939636 (10Aklapper) >>! In T1003#852987, @Dzahn wrote: > Access denied for user 'phstats'@... [...] This requires a change in DB GRANTS. @dzahn: Do... [12:50:12] 3Phabricator, Analytics-Tech-community-metrics, Engineering-Community: Monthly report of total / active Phabricator users - https://phabricator.wikimedia.org/T1003#939640 (10Dzahn) >>! In T1003#939636, @Aklapper wrote: > @dzahn: Does that require a separate ticket, or how to proceed? It does, but it already exi... [12:51:05] if you are thinking it's unclear what the difference is between being a "member" and being a "watcher" of a project, see [12:51:10] https://secure.phabricator.com/T6113 [12:56:29] 3Project-Management: Show percentage of teams migrated to Phabricator for project management - https://phabricator.wikimedia.org/T434#939649 (10Qgil) Last week [[ https://blog.wikimedia.org/2014/12/19/wikimedia-technical-operations-joins-the-phabricator-party/ | Operations migrated most of its RT tickets to Phab... [13:02:14] > but what is the point of maintaining the content at all? [13:02:59] JohnFLewis: we didn't migrate some data: https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla#Missing_data and https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla#Bugzilla_data_migrated [13:03:12] and some folks (I hope the number will decrease) might want to access such data. [13:05:13] andre__: now if we fixed the 'HTML stash' bug, would we also need the history of the bugs before BZ can be 'removed' once were sure there is nothing else? [13:05:29] Saved searches and votes could be handled via a db dump right? [13:07:59] if we can provide a sanitized DB dump on dumps.wm we should be fine [13:08:38] that would enable anyone to "fork" the data and come up with ideas [13:09:04] maybe even a replacement for saved searches in labs [13:09:08] if there is a demand [13:09:24] the problem is the "how to sanitize" part [13:10:19] just one example: if a bug _once_ was security relevant, but meanwhile is resolved, does it mean it can stay in the dump? [13:18:25] 3Wikibugs, Phabricator.org: Batch editing sends email updates - https://phabricator.wikimedia.org/T84964#939663 (10Aklapper) p:5Low>3Volunteer? >>! In T84964#937076, @Quiddity wrote: > /me twitches. I posted that number just for everybody's interest. I subscribed to all bugmail, hence I receive all bugmail.... [13:33:06] 3RT-Migration, operations: Migrate RT to Phabricator - https://phabricator.wikimedia.org/T38#939694 (10Dzahn) so it seems we decided to not import the domains queue. should/can i manually move an open ticket i was still working on? [13:55:18] 3Phabricator: Existing Phabricator user waiting 1 month for bugzilla activity to be assigned - https://phabricator.wikimedia.org/T85137#939727 (10Nemo_bis) 3NEW a:3chasemp [13:56:03] 3Phabricator: Existing Phabricator user waiting 1 month for bugzilla activity to be assigned - https://phabricator.wikimedia.org/T85137#939727 (10Nemo_bis) [14:02:12] sometimes i want to link directly to attachments uploaded in phab [14:02:47] the URLs are really cryptic and long though [14:03:17] and when i try to use them anyways i get a "File Link Has Expired" [14:04:05] https://phab.wmfusercontent.org/file/data/foo = Unhandled Exception ("Exception") [14:10:05] mutante: hmm, you should only get that for access restricted files that you cannot access [14:18:07] andre__: example: on https://phabricator.wikimedia.org/T76562 there is a screenshot. let's say i want to directly link to that [14:18:28] so i click on the image, get the pop-up thingie (like MediaViewer) [14:18:52] right-click, "Copy Image Location" [14:19:08] paste into browser [14:19:21] it works for a few seconds, then it expires [14:19:51] and "Continue to generate a new link to the file. You may be required to log in." [14:22:14] "it works for a few seconds, then it expires"? means it reloads the page?! [14:22:24] works here for more than a few seconds but maybe because I'm admin :-/ [14:23:16] it means i still get the image a second after i paste that, but if i wait just a few seconds and hit reload it's gone [14:23:29] ah, you hit Reload. [14:23:39] yeah, I can reproduce this. But why would you reload? [14:23:52] whatever token is passed, it probably is only valid once. [14:23:57] which makes sense to me. [14:24:02] 3Phabricator: Existing Phabricator user waiting 1 month for bugzilla activity to be assigned - https://phabricator.wikimedia.org/T85137#939792 (10chasemp) @platinodes, seems a ticket was made in your honor. Is there possibly a case situation here with the capital P and the emails in BZ and phab? Case mismatch... [14:24:03] yea, that would mean i cant use it at all [14:24:20] yeah. makes sense. [14:24:21] the purpose of a link would be to able to share it with others [14:24:29] you share the F12345 instead [14:24:34] i want to say "hey, X, look at this image" [14:25:10] ok, where do you get 12345 from ? [14:25:15] "Hey, look at this image: http://phabricator.wikimedia.org/F18152 " [14:25:32] 3Phabricator: Create a static HTML version of Bugzilla - https://phabricator.wikimedia.org/T85140#939794 (10JohnLewis) 3NEW a:3JohnLewis [14:25:33] you can work around that by using the link to the F number [14:25:50] finding the F number for an image in an initial task description requires "edit task" or "see raw" though [14:26:11] and if that's too complicated I'd link to the initial task description instead [14:26:16] oh, so you hit Edit Task [14:26:20] and then look at the source code [14:26:25] but yeah, this is how the access restrictions stuff works I guess - Link has expired... [14:26:40] to find out the F number for an embedded file preview in a task: yeah [14:26:45] why restriction on a public bug though? [14:26:59] ok, gotcha about the F: link, that works, thanks [14:27:06] I don't know the implementation details. :-/ [14:33:02] 3Phabricator, ops-core, operations: Sanitise a Bugzilla database du,p - https://phabricator.wikimedia.org/T85141#939806 (10JohnLewis) 3NEW [14:34:32] 3Phabricator, ops-core, operations: Sanitise a Bugzilla database dump - https://phabricator.wikimedia.org/T85141#939806 (10JohnLewis) [14:35:47] 3Phabricator: Bugzilla HTML static version and database dump - https://phabricator.wikimedia.org/T1198#939815 (10JohnLewis) 5Open>3Invalid a:3JohnLewis Split into T85140 and T85141 Not sure about the status so, invalid? [15:34:20] 3Phabricator: Bugzilla HTML static version and database dump - https://phabricator.wikimedia.org/T1198#939904 (10Dzahn) 5Invalid>3Open disagree. it's not invalid it's a tracking or master ticket which should have the 2 new tickets as subtasks/blockers [15:35:13] 3Phabricator: Bugzilla HTML static version and database dump - https://phabricator.wikimedia.org/T1198#939906 (10Dzahn) [15:35:37] mutante: I forget we have the concept of tracker tickets [15:38:53] 3Phabricator: Create a static HTML version of Bugzilla - https://phabricator.wikimedia.org/T85140#939915 (10Dzahn) example: if an old URL had this: show_bug.cgi?id=61294 then we would like to have something like: bug61294.html so one HTML page for each bug, starting from Bug 1 it should be done _without_ l... [15:41:35] 3Phabricator, ops-core, operations: Sanitise a Bugzilla database dump - https://phabricator.wikimedia.org/T85141#939917 (10Dzahn) The script looks reasonable. Where's a good place to test it though? It feels wrong to just use db1001 but also to copy the private data to labs or my personal laptop. [15:41:58] JohnFLewis: yep, i just used the "blocked by" [15:42:26] JohnFLewis: i'd simply try out the sanitizing script, but i'm unsure where to do it [15:45:03] mutante: I dont know really [15:45:17] i'm asking my team mates [15:49:55] JohnLewis: i'm gonna ask springle to give me a test db [15:50:03] which is a copy of the current db [15:50:12] kk [15:50:45] for now, I'm going to patch to move bugs-attachments to behind varnish along with other zirconium services [15:51:30] ok, just remember you cant move bugs-attachment without old-bz [15:51:39] well,maybe you could but it would be weird [15:51:47] hm? [15:52:36] it doesn't make sense to move the attachments elsewhere [15:52:46] while we keep the actual Bugzilla [15:53:08] attachements are just being put behind Varnish like Bugzilla currently is. No real changes [15:54:06] hmm. let me check that one more time. something tells me we had a reason for this [15:54:14] when we moved bz to old-bz [15:54:21] (reason for NOT moving both) [15:54:48] Check that out then and see if there was a reason [15:54:55] but yea, make the patches [15:55:04] the best kind of reminder to really check it [16:48:36] 3Phabricator, Phabricator.org: enotifs are sent from no-reply@phabricator.wikimedia.org - https://phabricator.wikimedia.org/T85127#940037 (10chasemp) Email allows a reply to header which means when you respond to these emails it doesn't go to the no-reply address. We never want someone to send mail to no-reply... [16:53:08] 3Phabricator, ops-core, operations: Sanitise a Bugzilla database dump - https://phabricator.wikimedia.org/T85141#940067 (10Dzahn) [17:04:22] 3Phabricator: Sending email to create tasks doesn't work for me - https://phabricator.wikimedia.org/T1077#940107 (10MarkAHershberger) >>! In T1077#939382, @Qgil wrote: > @MarkAHershberger can you test against http://secure.phabricator.org , please? For instance, trying to create this very same task there. This... [17:05:19] 3Phabricator: Sending email to create tasks doesn't work for me - https://phabricator.wikimedia.org/T1077#940110 (10MarkAHershberger) ah, but secure.phabricator.com does [17:30:12] 3Phabricator: Sending email to create tasks doesn't work for me - https://phabricator.wikimedia.org/T1077#940134 (10MarkAHershberger) opened https://secure.phabricator.com/T6799 [17:32:54] 3Phabricator.org: Sending email to create tasks doesn't work for me - https://phabricator.wikimedia.org/T1077#940137 (10Aklapper) [17:33:14] 3Phabricator.org: Sending email to create tasks doesn't work for me - https://phabricator.wikimedia.org/T1077#18676 (10Aklapper) [17:43:41] 3Phabricator.org: Sending email to create tasks doesn't work for me - https://phabricator.wikimedia.org/T1077#940144 (10MarkAHershberger) Upstreamed for now, but the upstream issue seems different. They have emails going to "bugs@" and that conflicts with a user named "bugs". We have emails going to "task@" an... [17:58:44] 3Phabricator: Existing Phabricator user waiting 1 month for bugzilla activity to be assigned - https://phabricator.wikimedia.org/T85137#940164 (10Aklapper) cf. T76169 - if that's the case, please change the capitalization of your email address under https://phabricator.wikimedia.org/settings/panel/email/ and wai... [17:58:52] 3Phabricator: Existing Phabricator user waiting 1 month for bugzilla activity to be assigned - https://phabricator.wikimedia.org/T85137#940168 (10Aklapper) a:5chasemp>3None [17:59:02] 3Phabricator.org: Sending email to create tasks doesn't work for me - https://phabricator.wikimedia.org/T1077#940170 (10MarkAHershberger) Note that upstream problem is resolved. There, the problem was a user named "bugs" that conflicted with the "bugs@" email address. There is no "task" user here. [17:59:38] 3Phabricator: Sending email to create tasks doesn't work for me - https://phabricator.wikimedia.org/T1077#940172 (10MarkAHershberger) [18:11:04] 3Phabricator: Testing T1077 - https://phabricator.wikimedia.org/T85157#940185 (10Qgil) 3NEW [18:13:51] 3Phabricator: Decide on "Needs Volunteer" Priority field value in Phabricator - https://phabricator.wikimedia.org/T78617#940194 (10Aklapper) >>! In T78617#937095, @Qgil wrote: > A term not mentioned in this thread is the term used for Low-1 by stock Phabricator and others: Wishlist. Renaming "Needs Volunteer" t... [18:17:26] 3Phabricator: Decide on "Needs Volunteer" Priority field value in Phabricator - https://phabricator.wikimedia.org/T78617#940199 (10Aklapper) [19:07:27] 3Phabricator: Decide on "Needs Volunteer" Priority field value in Phabricator - https://phabricator.wikimedia.org/T78617#940260 (10chasemp) what's funny is that that would mean we came full circle back to the defaults (wishlist) :) [19:26:09] 3Phabricator: Sending email to create tasks doesn't work for me - https://phabricator.wikimedia.org/T1077#940279 (10Qgil) In T85156 you created a task via email... [19:26:50] 3Phabricator, Spam-Spam: Testing T1077 - https://phabricator.wikimedia.org/T85157#940296 (10Qgil) 5Open>3Invalid [19:28:15] 3Phabricator: Sending email to create tasks doesn't work for me - https://phabricator.wikimedia.org/T1077#940299 (10chasemp) >>! In T1077#940279, @Qgil wrote: > In T85156 you created a task via email... I came here to say this :) Is the reply for the new task being nulled or trashbinned somewhere when returning? [19:30:19] 3RT-Migration, operations: Migrate RT to Phabricator - https://phabricator.wikimedia.org/T38#940301 (10chasemp) @dzahn, I would just ask @mark if he's cool w/ that? [19:30:52] 3RT-Migration, operations: Migrate RT to Phabricator - https://phabricator.wikimedia.org/T38#940302 (10chasemp) [19:31:51] 3Phabricator: Plan to migrate everything to Phabricator - https://phabricator.wikimedia.org/T13#940310 (10chasemp) [19:31:52] 3Project-Management: Process to request a private project - https://phabricator.wikimedia.org/T823#940309 (10chasemp) [19:31:54] 3RT-Migration, operations: Migrate RT to Phabricator - https://phabricator.wikimedia.org/T38#940305 (10chasemp) 5Open>3Resolved well we migrated so to the extend remaining work in T76990 is left it can't be a blocker :) There are more things down the road but they should probably have their tickets. [19:45:04] 3RT-Migration: Only first requestor of RT tickets with several requestors got migrated to Phab task author - https://phabricator.wikimedia.org/T84828#940321 (10chasemp) a:3chasemp [19:46:21] 3Phabricator: Next Phabricator upgrade on YYYY-MM-DD (to be defined) - https://phabricator.wikimedia.org/T78243#940327 (10chasemp) a:3chasemp [19:59:28] 3Phabricator: Upgrade phab-01 to use the same version as production Phabricator - https://phabricator.wikimedia.org/T78168#940370 (10chasemp) 5Open>3Resolved a:3chasemp So the instance needs a bit of love but for the moment I updated it to the production tag. [20:29:09] chasemp: I've got the extensions updated on fabapi [20:29:47] "HEAD is now at 3b337d7... Huge refactor of security policy enforcer stuff." [20:34:32] 3RT-Migration: Only first requestor of RT tickets with several requestors got migrated to Phab task author - https://phabricator.wikimedia.org/T84828#940417 (10chasemp) a:5chasemp>3Aklapper thanks! [20:35:08] twentyafterfour: ok man! I don't have a ton of time this afternoon but first thing a.m. I will try to run through [20:35:11] looks good so far tho [20:35:26] oh well, I hope to do this before xmas but we'll see [20:35:33] got the default change at least [20:37:14] chasemp: it's fairly well tested locally on my dev machine [20:37:51] I should make some unit tests for that security stuff [20:38:56] 3RT-Migration: RT migrated tasks have Security: None but are visible/editable to WMF-NDA only - https://phabricator.wikimedia.org/T84985#940424 (10Qgil) [20:38:57] 3RT-Migration: RT migrated tasks have Security: None but are visible/editable to WMF-NDA only - https://phabricator.wikimedia.org/T84985#935980 (10Qgil) [20:39:30] 3RT-Migration: RT migrated tasks have Security: None but are visible/editable to WMF-NDA only - https://phabricator.wikimedia.org/T84985#940427 (10Qgil) 5Open>3Invalid a:3Qgil This was intended. Resolving as Invalid. [20:40:00] 3Phabricator: Prevent private information being leaked via Herald notifications - https://phabricator.wikimedia.org/T493#940430 (10Qgil) [20:43:06] 3RT-Migration, operations: Update wiki documentation related to RT - https://phabricator.wikimedia.org/T76990#940442 (10Qgil) The part of this task strictly related with the RT migration (basic update of links and references to RT / Bugzilla i solved. The remaining work is basically about documenting the new pr... [21:12:47] <^d> chasemp, twentyafterfour: my elastic stuff just landed upstream \o/ [21:13:03] * ^d should not know this, me is on vacation [21:24:30] https://phabricator.wikimedia.org/tag/tool_labs/ is archived? [21:26:17] it's even worse: it doesn't even show up in gray in the new task window... [21:28:39] qgil: https://phabricator.wikimedia.org/T85168 [21:29:05] Krenair, which project are you looking for? [21:29:08] matanya, thanks! [21:29:28] sure, sorry it took so long, real life gets in the middle [21:29:28] andre__, where to put issues with the tools project in labs [21:29:50] Krenair, Tool-Labs [21:30:13] ah, ok :/ [21:30:48] andre__, Krenair: fixed now by adding #toollabs as hashtag to tool-labs [21:31:00] the issue was that entering 'toollabs' in autocorrect gave you 'tool labs' instead [21:31:27] meh... I more and more dislike the autocomplete proposals [21:31:28] thanks [21:32:19] it's not too weird to hide 'tool-labs' if someone enters 'toollabs' [21:32:31] just in this case it's confusing because 'tool_labs' /is/ shown [21:57:16] <^d> andre__: wmf-nda group. what's the procedure for someone who's got an nda to get added to said group? [21:58:32] ^d: https://phabricator.wikimedia.org/tag/wmf-nda/ says Contact operations if you believe you should be a member. [21:58:48] * ^d nods [21:58:49] <^d> Thanks [22:00:10] ^d: https://wikitech.wikimedia.org/wiki/Talk:Volunteer_NDA#Create_a_request [22:00:42] <^d> Not a volunteer. [22:00:43] <^d> :) [22:01:03] oh, ignore me then :) [22:17:03] 3Phabricator: Edit policy should always be the same as view policy - https://phabricator.wikimedia.org/T85171#940637 (10Krenair) 3NEW [22:18:10] qgil: you broke my attempt to exploite :P [22:20:35] 3Phabricator, Phabricator.org: Can't search an exact phrase in Phabricator - https://phabricator.wikimedia.org/T75743#940650 (10Chad) This was merged upstream. [22:20:54] 3Phabricator, Phabricator.org: Phabricator search does not search substrings - https://phabricator.wikimedia.org/T679#940651 (10Chad) This was merged upstream. [22:24:07] ^d: awesome glad that landed, it's a big improvement I think [22:25:49] <^d> Yeah. We'll have to reindex everything but it'll make landing changes to the mapping way easier in the future. [22:25:54] <^d> Much smaller delta. [22:27:11] 3Phabricator: Edit policy should always be the same as view policy - https://phabricator.wikimedia.org/T85171#940663 (10mmodell) edit policy and view policy are distinct for a reason. There are legitimate use cases for having them be different. Proposing declined. [22:28:04] 3Phabricator: Edit policy should always be the same as view policy - https://phabricator.wikimedia.org/T85171#940669 (10Krenair) What legitimate use cases? [22:29:44] 3Phabricator.org: Add IRC name and MediaWiki Username as alternate auto-complete lookups - https://phabricator.wikimedia.org/T877#940691 (10mmodell) @chad just landed some elasticsearch stuff upstream that might be helpful here. [22:30:45] 3Phabricator.org: Add IRC name and MediaWiki Username as alternate auto-complete lookups - https://phabricator.wikimedia.org/T877#940693 (10Chad) Probably not, beyond "it's now easier to make changes to this code" :) [22:32:56] 3Phabricator, Phabricator.org: Can't search an exact phrase in Phabricator - https://phabricator.wikimedia.org/T75743#940696 (10Qgil) [22:33:05] <^d> twentyafterfour: The cooler thing we got was switching to using http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-simple-query-string-query.html [22:33:16] <^d> It greatly expands the syntax the user can type in. [22:33:46] 3Phabricator: Edit policy should always be the same as view policy - https://phabricator.wikimedia.org/T85171#940698 (10RobH) There is no reason for every phab user to be able to set the priority of our onsite (or team level) tickets/tasks. These are set via team priority and tasking, involving a lot of factors... [22:33:58] 3Phabricator, Phabricator.org: Phabricator search does not search substrings - https://phabricator.wikimedia.org/T679#940700 (10Qgil) [22:35:13] ^d awesome. [22:36:52] is there any migration needed or do we just pull the upstream revision and we're good? [22:37:28] <^d> Have to totally rebuild the index. [22:37:37] <^d> `./bin/search init` [22:37:50] <^d> `./bin/search index --background` or w/e the param is named. [22:39:10] 3Phabricator: Edit policy should always be the same as view policy - https://phabricator.wikimedia.org/T85171#940722 (10Krenair) Ops is not special, all other WMF teams manage. [22:39:40] <^d> twentyafterfour: It's analysis changes that require reindexing usually. [22:40:20] qgil, hi [22:40:59] <^d> Ok, vacation time for real. Adios folks. [22:41:22] 3Phabricator: Edit policy should always be the same as view policy - https://phabricator.wikimedia.org/T85171#940734 (10Qgil) More legitimate cases. By default, Phabricator tasks are visible to Public (anonymous included) but editable by All Users (logged in only). This difference seems appropriata, and is the... [22:41:45] 3Phabricator: Edit policy should always be the same as view policy - https://phabricator.wikimedia.org/T85171#940735 (10Qgil) p:5Triage>3Normal [22:56:57] 3Phabricator: Edit policy should always be the same as view policy - https://phabricator.wikimedia.org/T85171#940771 (10Krenair) > More ? > By default, Phabricator tasks are visible to Public (anonymous included) but editable by All Users (logged in only). This difference seems appropriata, and is the same dif... [22:59:50] 3Phabricator: Edit policy should (almost) always be the same as view policy - https://phabricator.wikimedia.org/T85171#940784 (10Krenair) [23:07:55] 3Wikibugs: wikibugs test bug [23:08:23] 3Wikibugs: wikibugs test bug [23:08:43] 3Wikibugs: wikibugs test bug [23:09:12] 3Wikibugs: wikibugs test bug - https://phabricator.wikimedia.org/T1152#19999 (10valhallasw) [23:12:48] 3Wikibugs: wikibugs test bug [23:12:58] lol [23:18:44] Krenair: and this is what we call IRC injection ;-) [23:18:50] :d [23:18:52] :D [23:22:14] 3Wikibugs: wikibugs fails to link Phab task in some IRC notifications - https://phabricator.wikimedia.org/T76650#940827 (10Legoktm) 5Open>3Resolved a:3Legoktm Fixed by https://gerrit.wikimedia.org/r/#/c/181523/ [23:23:32] 3Wikibugs: wikibugs test bug - https://phabricator.wikimedia.org/T1152#940830 (10Legoktm) [23:29:49] 3Phabricator, Phabricator.org: We need a Wikimedia process for filing tasks and patches upstream in the name of Wikimedia - https://phabricator.wikimedia.org/T1298#940866 (10Qgil) p:5Normal>3High [23:36:20] 3Phabricator: "Project creation log" cronjob email for Phab admins - https://phabricator.wikimedia.org/T85183#940900 (10Aklapper) 3NEW a:3Aklapper