That's a reasonable point. The details of PHI386 weren't very indicative one way or another since I didn't end up GC'ing the repository multiple times. I suppose I can go GC it again during the deployment window this week and see how long it takes.

Previously, in PHI386, an unusually large repository for the same instance took about 5 hours to git gc.

Modify the PushEvent table to contain more information about locks and waits (e.g., active queue status; how long the push waited for the write lock; how long the push spent synchronizing).

These people are good, I like them.

I kind of wish I could see PHI415. Do people send in support tickets about path of exile?

@epriestley wrote:

See PHI415.

Wow I feel unethical looking at your profile now.

wow every piece of gear you have is better than all the gear I own put together

Nice nice. I've had a few kaoms and some other opop 1000% unethical gear because I've never made it past act 1 in TRUE ETHICAL SSF.

See PHI431. See PHI426. ... I suspect these lead to T731 and T10574, practically.

See PHI483. There's currently a bad interaction between builds completing and drafts unpublishing, described in greater detail in T13108.

On complex build statuses, which has come up more than a handful of times but which I haven't aggregated well:

(Note that it will only work for more-recent logs, T13088 will have some guidance for older logs eventually.)

I missed this task when collecting T13088, but this is supported after D19151.

This is sort of a race. Here's what happens:

I only play True Ethical SSF Hardcore so I have of never seen a Kaom's or worn a piece of gear with more than 4 links on it, and I'm definitely not very good at the game, but one thing that's been going better for me this league is that I've been doing builds with critical strike.

People here play path of exile? noice. I think I got to like, level 30 in beastiary, then started playing in standard again.

D19240 exhibited the same behavior on a local lint failure so this is almost certainly a mundane bug rather than some sort of exotic race.

I had a local test failure there

From reading the code, the behavior should already be (A): that is, we should already get this right in cases (3) and (4).

See PHI483. Some of the mail rules around builds and drafts are kind of whack right now.

I removed this in rCORE36d2ef5dffe441ba1175e362bb73f0e43a9f70a2.

See also T13102/PHI442. The MySQL setting optimizer_search_depth=0 may fix the weird explosive complexity here.

The Arc Hierophant is still alive, but he managed to get a Scaeva to drop shortly after the last update. I brought a Reave Juggernaut to 82 with it, although I've only made 1-2 tiers of progress in maps.

Ideally, I think Diffusion, Files and Paste should all have the highlighting/encoding options and share more of the same code, with Diffusion being distinguished by having blame (and, I suppose, symbol linking) available.

I'm wondering how this should interact with T8407: Control diffusion's syntax highlighting.

In T8135#195972, @johnny-bit wrote:

Maaaybe Iam misinterpreting but if enabling sort by priority why not show in workboards something like [...]

It would be great if there was an ability for installations to write custom viewers for formats that are either more obscure (MIF Framemaker format), or even in house formats (.myformat)

I don't run my Phabricator instance on Ubuntu but instead on RHEL6 (and with PHP7, which I know isn't officially support)

For what it's worth, after spot-checking a few tasks on my install, all seem to query the same policy 10ish times in succession near the end of the load.

The task.open-count.status counts open tasks that are the result of a status change (an existing task being closed, or a closed task being reopened). Since it's much more common for existing open tasks to be closed than for existing closed tasks to be reopened, the series should go negative pretty quickly and stay there over time, more or less ending up with a big negative number of "number of tasks ever closed".

Not sure if it's expected in the current state, but here's one that doesn't seem well-formed: https://secure.phabricator.com/fact/chart/?y1=tasks.open-count.status

If writing, deploying, and maintaining this server doensn't seem like much work to you (and it may reasonably not be), write this server yourself and replace the pygmentize binary on your system with a lightweight client written in a language with a fast startup time that just calls through to the server.

aaaannnndddd..... I found it. D19050

What steps did you take to try to find the documentation?

We currently use this extension at BisManOnline to integrate with our CRM system. Also, I believe that the Phabulous Slack Bot uses it as well https://github.com/etcinit/phabulous

See PHI364. An install encountered a held lock issue...

See PHI364. An install encountered a held lock issue in a cluster which resolved itself immediately when I appeared onsite.

is there a chance that this problem will get fixed?
The change D17989 is already from May 2017 without any reviewer...

Having looked at the code some more, I see when the HeraldPreCommitRefAdapter runs, there is no parsed commit object yet, so there's no way to invoke harbormaster (what would the container PHID be?). This kind of makes sense.