[00:05:02] "All tokens have been replaced with boars. πŸ—" [00:05:05] from Phabricator changelog [00:05:09] what are boars [00:05:49] Not sure [00:05:57] but were about to find out [00:05:58] :) [00:06:01] :) [00:10:14] twentyafterfour what does it mean by ^^ [00:10:19] please [00:12:33] huh [00:13:09] twentyafterfour from the changelog at https://secure.phabricator.com/w/changelog/2016.27/ [00:13:15] it says β€’All tokens have been replaced with boars. πŸ— [00:14:03] it's a reference to the new Token spritesheet [00:14:19] they haven't really been replaced with boars...it's just epriestley's humor [00:14:26] oh [00:14:31] thanks for explaning [00:14:34] :) [00:15:48] haha, thanks:) [00:17:45] The new task graph is awesome: https://phabricator.wikimedia.org/T94620 [00:18:15] oooh ! [00:18:24] really nice [00:18:32] twentyafterfour it seems to show a task that is not accisable [00:18:36] https://phabricator.wikimedia.org/T70271 [00:18:42] ο‚ˆ Declined None [00:18:42] T4007 [DO NOT USE] Tracking bug [superseded by the #Tracking tag] [00:18:42] T4007: [DO NOT USE] Tracking bug [superseded by the #Tracking tag] - https://phabricator.wikimedia.org/T4007 [00:18:59] doint even rember that task even being added to the gerrit 2.12 task [00:19:13] https://phabricator.wikimedia.org/T4007 [00:19:19] http 500 error [00:19:19] 10Phabricator: Paste search shows wrong length - https://phabricator.wikimedia.org/T140324#2460312 (10Mattflaschen-WMF) [00:20:27] weird [00:20:43] Yep [00:21:01] that must be an especially epic epic [00:21:27] twentyafterfour I wish there was support for us to remove things from the graph. [00:21:30] please [00:21:47] paladox: there is [00:21:53] edit related tasks [00:21:56] Oh [00:22:32] Do you know where the task is please. [00:22:36] :) [00:23:23] It's very hard to tell what task's block the task [00:23:27] and which are sub tasks [00:23:31] :) [00:28:54] 10Phabricator: Phabricator task graphs need a limit on how big they draw - https://phabricator.wikimedia.org/T140326#2460337 (10Paladox) [00:46:57] Wheeeeee! (also, it's really bad on some otherwise normal tasks. e.g. I get a script timeout every time I try to load https://phabricator.wikimedia.org/T126641 [00:58:00] 10Phabricator: T126641 won't load - https://phabricator.wikimedia.org/T140328#2460373 (10kaldari) [01:00:12] 10Phabricator: T126641 won't load - https://phabricator.wikimedia.org/T140328#2460391 (10Quiddity) [01:25:25] i was trying to prevent the issues with big dependency graphs, but got blocked in my effort :-/ [01:40:29] Danny_B, track ALL the things! >.> [01:48:19] twentyafterfour: gonna revert the upgrade? [03:26:23] Danny_B: I'm gonna try to fix it [03:26:28] no revert! [04:03:13] i'm removing T4007 from dozens of tasks. It helps a lot in some cases (narrowing the tree, to make the words visible). Still can't view 4007 itself though [04:03:14] T4007: [DO NOT USE] Tracking bug [superseded by the #Tracking tag] - https://phabricator.wikimedia.org/T4007 [04:22:52] quiddity: I've applied a hotfix provided by epriestley which disables the graph when there are more than 100 related tasks [04:25:24] twentyafterfour, aha! And https://phabricator.wikimedia.org/T4007 is visible now. [04:25:52] I wish I'd taken more screenshots of the hilarity! ;-) [04:40:35] < twentyaft> The new task graph is awesome: https://phabricator.wikimedia.org/T94620 [04:40:42] heck yeah, that's great! [04:42:21] quiddity: are you going to remove them all? (the subtasks?) [04:43:08] I... I might be able to make sense of some epics/big projects... [04:43:23] * greg-g is manager excited right now, apologizes [04:44:41] greg-g, no, i was just trying to make a dent, so that 4007 itself became visible (it was timing out after 10 seconds and just showing an ascii tableflip.), and so that some of the trees with excessively wide views became fixed (per my screenshots in https://phabricator.wikimedia.org/T140326#2460876 ) I'll leave the rest up to wider discussion, and/or someone else, and/or morning. (I just realized it's almost 10pm, and I haven't had [04:44:41] dinner....) [04:44:57] also, yes! Treeeeees! [04:45:48] nemo showed me how dependency trees worked in bugzilla, a few months before we transitioned to phab. i've been looking forward to getting these. :) [04:50:29] quiddity: yeah, they were there, but hard to navigate around and, as with all things BZ, quite ugly [05:15:52] indeed the trees are awesome. And no longer completely broken [06:58:23] quiddity: when you were removing 4007, were you checking for the presence of #tracking tag? [07:00:04] Danny_B, I was finding 90% of them by opening tasks in the #tracking workboard. [07:00:33] 10Phabricator, 07Regression: Regression: list of blocked/blocking tasks disappeared - https://phabricator.wikimedia.org/T140333#2460961 (10Nemo_bis) [07:02:08] 10Phabricator, 07Regression: Regression: list of blocked/blocking tasks disappeared - https://phabricator.wikimedia.org/T140333#2460961 (10Danny_B) That's temporary hack ATM because of {T140326}. [07:02:43] 10Phabricator, 07Regression: Regression: list of blocked/blocking tasks disappeared - https://phabricator.wikimedia.org/T140333#2460961 (10Quiddity) See T140326#2460857 for some context., plus discussion in -devtools and -operations. [07:03:22] oh whoops, you'd already replied. ah well, i should sleep anyway. o/ [07:03:24] faster, faster ;-) [07:03:39] hehe :) [07:12:17] 10Phabricator: Inconsistent terminology subtask/parent task - https://phabricator.wikimedia.org/T140335#2461017 (10Nemo_bis) [07:14:38] 10Phabricator, 07Regression: Regression: list of blocked/blocking tasks disappeared - https://phabricator.wikimedia.org/T140333#2461032 (10Nemo_bis) >>! In T140333#2460981, @Danny_B wrote: > That's temporary hack ATM because of {T140326}. Thanks. Reverting to known-working Phabricator code would have been bet... [07:16:15] 10Phabricator: Disable blogs on Phabricator - https://phabricator.wikimedia.org/T135689#2461033 (10Nemo_bis) 05declined>03Open There is no argument for keeping them either. [07:29:33] 10Phabricator, 07Regression: Regression: list of blocked/blocking tasks disappeared - https://phabricator.wikimedia.org/T140333#2461066 (10Peachey88) [08:58:05] 10Phabricator, 07Regression: Regression: list of blocked/blocking tasks disappeared - https://phabricator.wikimedia.org/T140333#2461263 (10mmodell) p:05Triage>03Low This is hardly an unbreak! now issue. See {T140207} [11:31:46] 10Phabricator: Phabricator no longer displays blocking tasks if there are more than 100 of them - https://phabricator.wikimedia.org/T140351#2461630 (10matmarex) [11:53:44] 10Phabricator: Disable blogs on Phabricator - https://phabricator.wikimedia.org/T135689#2461700 (10Aklapper) 05Open>03declined Argument is that people are free to use it. [12:26:47] 10Phabricator, 10TPG-Essential-Functions, 06Team-Practices, 06Developer-Relations (Jul-Sep-2016), 07Documentation: Update phab docs to reflect new parent/subtask terminology - https://phabricator.wikimedia.org/T139181#2461724 (10Aklapper) 05Resolved>03Open And it's outdated again due to yesterday's d... [12:36:17] 10Phabricator, 10TPG-Essential-Functions, 06Team-Practices, 06Developer-Relations (Jul-Sep-2016), 07Documentation: Update phab docs to reflect new parent/subtask terminology - https://phabricator.wikimedia.org/T139181#2461749 (10Aklapper) 05Open>03Resolved Whacking a mole, hope this won't change agai... [13:21:04] 10Phabricator, 06ArchCom, 06Developer-Relations, 06Release-Engineering-Team, 06Team-Practices: Consider alternative processes for Unbreak Now bugs, especially those which cross-cut components - https://phabricator.wikimedia.org/T140207#2456573 (10Danny_B) [[ https://phabricator.wikimedia.org/maniphest/qu... [14:30:30] 10Phabricator: Show more info about restricted tasks in task dependecy graph - https://phabricator.wikimedia.org/T140362#2462091 (10Danny_B) [14:34:03] 10Phabricator: Show more info about restricted tasks in task dependecy graph - https://phabricator.wikimedia.org/T140362#2462091 (10matmarex) I think this is the expected behavior. If there was a tracking task like "Refactor authentication code", and it had an unbreak-now priority blocker, that's a clear indicat... [14:34:31] 10Phabricator: Show more info about restricted tasks in task dependecy graph - https://phabricator.wikimedia.org/T140362#2462134 (10matmarex) 05Open>03declined Upstream is right. [14:37:27] 10Phabricator: Phabricator no longer displays blocking tasks if there are more than 100 of them - https://phabricator.wikimedia.org/T140351#2462153 (10matmarex) For a more practical example, I can no longer see the subtasks of T107037. I think this is a major issue. [14:41:05] 10Phabricator: Show more info about restricted tasks in task dependecy graph - https://phabricator.wikimedia.org/T140362#2462173 (10Danny_B) 05declined>03Open >>! In T140362#2462131, @matmarex wrote: > I think this is the expected behavior. If there was a tracking task like "Refactor authentication code", an... [14:42:22] 10Phabricator: Show more info about restricted tasks in task dependecy graph - https://phabricator.wikimedia.org/T140362#2462190 (10matmarex) Please read carefully what //I// wrote. Do you see anything about task titles? I'm talking about a public parent (tracking) task, and private subtask. [14:42:30] 10Phabricator: Show more info about restricted tasks in task dependecy graph - https://phabricator.wikimedia.org/T140362#2462191 (10matmarex) 05Open>03declined [15:15:09] 10Phabricator: Phabricator no longer displays blocking tasks if there are more than 100 of them - https://phabricator.wikimedia.org/T140351#2462357 (10greg) [17:03:09] [Diffusion] [Committed] rOPUP9a90d266334c: admin: add test for absented users not in 'absented' group [17:03:13] twentyafterfour: so the emails when I only rebase a changest that say ^ [17:03:31] these are really going to get confusing as more ppl move to differential where that messge means a totally different thing happened [17:03:37] and really it's confusing now I think [17:07:05] chasemp: agreed, see also the task that started this: https://phabricator.wikimedia.org/T89940 [17:07:54] I never really found it valuable :D but now I think it may be actively harmful [17:11:00] 10Phabricator: Disable blogs on Phabricator - https://phabricator.wikimedia.org/T135689#2462757 (10Nemo_bis) 05declined>03Open > Argument is that people are free to use it. This is not an argument, it's a statement. [17:17:43] 10Phabricator: Disable blogs on Phabricator - https://phabricator.wikimedia.org/T135689#2462809 (10Luke081515) And currently no argument here to disable working infrastructure. > "Never change a running system" [17:18:41] 10Phabricator: Disable blogs on Phabricator - https://phabricator.wikimedia.org/T135689#2462825 (10Aklapper) 05Open>03declined You seem to be the only person so far requesting to disable it so I'd expect arguments to be provided but so far I have not seen any, and T135689#2308782 has remained unanswered. Pl... [17:26:19] 10Diffusion, 05Gitblit-Deprecate, 06Release-Engineering-Team, 07WorkType-NewFunctionality: Use Diffusion as canonical location for browsing code repos (not gitblit) - https://phabricator.wikimedia.org/T752#2462948 (10greg) [17:26:22] 10Diffusion, 05Gitblit-Deprecate: Replicate open patchsets to diffusion - https://phabricator.wikimedia.org/T89940#2462946 (10greg) 05Resolved>03Open (Reopening while we discuss this.) >>! In T89940#2451956, @Paladox wrote: > @bd808 we could stop those commits from being linked in tasks through an update... [17:27:45] chasemp: ^ :) [17:34:58] 10Diffusion, 05Gitblit-Deprecate: Replicate open patchsets to diffusion - https://phabricator.wikimedia.org/T89940#2463071 (10demon) >>! In T89940#2462946, @greg wrote: >> On IRC @Paladox made a claim that the external viewer links are valuable for reviewing code from phones and other unspecified user-agents t... [17:38:40] 10Diffusion, 05Gitblit-Deprecate: Replicate open patchsets to diffusion - https://phabricator.wikimedia.org/T89940#2463083 (10mmodell) The one use case I have for `refs/changes` in phabricator is for converting gerrit unmerged changes into differential diffs. [17:40:54] 10Diffusion, 05Gitblit-Deprecate: Replicate open patchsets to diffusion - https://phabricator.wikimedia.org/T89940#2463085 (10demon) >>! In T89940#2463083, @mmodell wrote: > The one use case I have for `refs/changes` in phabricator is for converting gerrit unmerged changes into differential diffs. There's a d... [17:44:59] greg-g: https://secure.phabricator.com/T4788#185867 - not that it would be easier now, actually... cf. https://phabricator.wikimedia.org/T139210 discussion [17:46:16] it is way easier now, there are far more tags/projects in phab than there were in BZ, and that's good (I think, at least) [17:46:47] also, tags are way more useful in phab than the components in BZ (a bug could be in only one component) [17:46:59] but yeah, I say the obvious :) [17:47:49] I had forgotten this and you made me remember [17:47:49] We even had a meta tracking task, which all of the tracking tasks were blockers of. [17:47:50] dang it [17:47:52] lunch now [17:47:56] yep [17:47:59] :) [17:48:04] 2007 [17:48:08] (bug 2007) [17:53:53] 10Diffusion, 05Gitblit-Deprecate: Replicate open patchsets to diffusion - https://phabricator.wikimedia.org/T89940#2463162 (10mmodell) >>! In T89940#2463085, @demon wrote: >>>! In T89940#2463083, @mmodell wrote: >> The one use case I have for `refs/changes` in phabricator is for converting gerrit unmerged chan... [17:55:02] greg-g: i would agree with you in a situation when it was true. you are forgotting that some tags are being discussed for ages, some have been even rejected (although they were to replace some quite huge tracking bug) [17:56:42] until the creation of tags isn't blocked just because of "i don't see a reason for the tag" we will never get rid of tracking tasks, which was my original intention (and knowing these graphs will be the issue was one of the reasons why i was trying to do that) [17:58:35] I don't think we need to get rid of all tracking tasks [17:58:49] some are useful and not worthy of projects [18:02:26] maybe just "tracking tasks with lots of subtasks" should be converted, some smaller ones are useful. [18:02:44] those are typically not with many tracked tasks which have subtasks etc... [18:03:53] greg-g: by definition, tracking task is the task which will never get closed. so obviously the number of tracked tasks will raise during the time [18:04:50] the major issue is, that people call any task which has subtasks a tracking task no matter that it is just task with simply clearly defined endpoint [18:05:23] hence why i wanted to re-mark those with #goal [18:05:29] unsuccessfully :-/ [18:06:28] or epic [18:06:54] I think there's some inconsistency there. If a tracking task will never get closed then it calling it a goal isn't useful. Maybe call it #sisyphus instead? ;) [18:07:41] There are tracking tasks which will be closed (eg: "get rid of Ubuntu Precise machines in production") [18:08:12] or is that not a 'tracking task' in the ontology your using? [18:09:18] I think so, re-reading the above [18:09:19] greg-g: no, you didn't understand me [18:09:41] so, "get rid of Ubuntu precise" is a tracking task and should have been a project? [18:10:01] i didn't want to tag real tracking tasks with #goal, but those which aren't tracking [18:10:43] "get rid of Ubuntu precise" is a task, which should not carry #tracking tag but (non existing) #goal tag [18:10:51] I see [18:10:56] meeple27: yeah, and epics / stories [18:11:29] the term "tracking tasks" is baffling to anyone who didn't experience them in bz, I think [18:11:54] greg-g: but my long time try to do that is constantly being undermined [18:11:55] summary in my head, given the confusion I think this could all use some documentation before making big changes so that people are not surprised [18:12:55] I would favor deprecating the term "tracking tasks", rather than trying to agree on and teach the definition...especially when the point is to teach people what NOT to do [18:13:01] Danny_B: i think it's mostly because people aren't seeing the bigger goal that you have in your head (I at least, have only seen snippets of it in various task comments) [18:13:08] agree, but for the documentation, you need at least one working example. which you won't have without the tag. which you won't get without approval which you won't get without documentation... what was earlier? egg or hen? [18:13:23] no, you can document before you do [18:13:35] it's called a plan/project proposal ;) [18:15:54] meeple27: that was my goal - get completely rid of them by swithing them to more appropriate representation (cf. #tracking workboard for breakout) [20:35:41] Pinged by #sisyphus. <_< [20:38:55] Debra: really? odd stalk word :) [20:43:00] 10Phabricator, 06Operations: Phabricator weekly report not generated (or at least sent) - https://phabricator.wikimedia.org/T139950#2463947 (10mmodell) @jcrespo: I thought we were ready to go ahead with the failover and then we could reenable the cron jobs afterward. @greg, @danny_b: I'll run the job manual... [20:43:29] 10Phabricator, 06Developer-Relations, 06Project-Admins, 07RfC: Abandon project creation policy - https://phabricator.wikimedia.org/T139210#2463949 (10Danny_B) @tto Also {T103700}. [20:45:36] 10Phabricator, 06Operations: Phabricator weekly report not generated (or at least sent) - https://phabricator.wikimedia.org/T139950#2447582 (10Dzahn) Why don't you just enable the report separate from the other maintenance things? It's a separate thing that is sent to "absent' anyways. ``` 190 # project... [21:42:24] meeple27: you will have to teach a lot of old dogs your new tricks. :) [21:43:00] 10-15 years of institutional memory is hard to overcome [21:57:20] 10Wikibugs: Do not notify #Trash tasks to IRC - https://phabricator.wikimedia.org/T140426#2464291 (10Danny_B) [22:30:49] 10Phabricator: Need replacement for "task graph" for tasks with big graphs - https://phabricator.wikimedia.org/T140428#2464505 (10Smalyshev) [22:31:57] 10Wikibugs, 13Patch-For-Review: Do not notify #Trash tasks to IRC - https://phabricator.wikimedia.org/T140426#2464533 (10Legoktm) 05Open>03Resolved a:03Legoktm [22:41:20] 10Phabricator: Need replacement for "task graph" for tasks with big graphs - https://phabricator.wikimedia.org/T140428#2464589 (10greg) [23:06:23] 10Phabricator, 06Operations: Phabricator weekly report not generated (or at least sent) - https://phabricator.wikimedia.org/T139950#2464662 (10mmodell) Ok, I just ran the community_metrics script manually. >>! In T139950#2463954, @Dzahn wrote: > Why don't you just enable the report separate from the other m... [23:10:09] tracking task is common, not just in Bugzilla [23:10:25] remembers them from JIRA f.e. [23:10:42] i think it's a general bugtracker thing [23:12:47] greg-g: https://phabricator.wikimedia.org/T140333#2464618 i am not sure if it was upstream patch, i think twentyafterfour hacked it himself [23:13:45] mutante: in fact it is a workaround for other features [23:14:03] which are either missing or difficult to work with [23:15:51] Danny_B: https://phabricator.wikimedia.org/T140326#2460879 [23:19:54] ok, thx [23:20:43] thx for the detailed description [23:23:39] 10Phabricator, 06Operations, 13Patch-For-Review: Phabricator weekly report not generated (or at least sent) - https://phabricator.wikimedia.org/T139950#2464720 (10Danny_B) And the weekly stats? [23:25:52] 10Phabricator, 10DBA, 06Operations, 13Patch-For-Review: Upgrade m3 (phabricator) db servers - https://phabricator.wikimedia.org/T138460#2464723 (10jcrespo) I do not feel confident with the current status- while I could rush it and do it today (the slave is ready), after checking that this shard is not yet... [23:27:30] 10Phabricator, 10DBA, 06Operations, 13Patch-For-Review: Upgrade m3 (phabricator) db servers - https://phabricator.wikimedia.org/T138460#2464725 (10jcrespo) [23:47:58] mutante: I have been in sw dev for decades, but hadn't heard the term "tracking task" until arriving here [23:48:18] not saying I'm omiscient; just that it's somewhere between "only here" and "everywhere"