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".

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

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.

Some of this got fixed, some ended up in T13081.

With that stuff, we're down from 473 to 227 on T9950. That's still awful, but not quite as ridiculous.

See T13069 for mail stamp plans.

This was largely tackled above.

I'm having some difficulty merging (5) and (6), or either of them into (2). My local test also has a lot of nonsense going on that a real install shouldn't. I'm going to land what I've got so far and see how much progress we've made here.

Queries are down to 139 for me locally.

Queries are now down from 151 to 145 for me locally.

Next problem:

For my local test task (T369), the initial page query load was 199 queries. After D19222 we're down slightly to 151 queries.

Some of this is:

This was resolved by the introduction of PhabricatorExtendedPolicyInterface. Older cases with missing policy proxies occasionally crop up, but I believe most of them are resolved at HEAD of master. These errors always fail closed (deny access which should be acceptable), never fail open (allow impermissible access) so there's no urgency to hunting them down.

See followup in T13105.

See followup in T13105.

(I'll follow up in T13102 if there's more to be done here, it's possible that some installs are missing this for reasons other than "Ubuntu + apt get install php5-mysql").

It appears that MYSQLI_ASYNC depends mostly on mysqlnd ("MySQL Native Driver"). This has been the default since PHP 5.3 was released in 200 BC, but Ubuntu, at least, unbundles it and you can still install php5-mysql (non-native driver). Compounding this, we currently recommend installs install php5-mysql (bad), rather than php5-msyqlnd (good).

After D19191 it would be relatively easy to support projects and wildcard functions (like "Any Repository") but there's currently no interest in this from customers.

While testing D19215 I ran into this behavior in Asana:

I wasn't able to reproduce the black background issue, exactly, but here's what I changed:

Thanks, I wasn't able to puzzle out the reproduction instructions on the original report since they didn't mention actually making any policy changes.

(This still needs documentation and validation for the configuration option before it's done, but I don't have any short-term plans to pursue those.)

To customize this: