Harbormaster needs a "Working Copy" blueprint, not just a "Host" blueprint.

This is almost certainly "PhabricatorMetaMTAReceivedMail incorrectly assumes email is valid UTF8", and the solution begins by making all the associated storage binary, but it's hard to imagine that ever happening now.

Difficult to imagine this ever getting fixed in the upstream since I don't have any Android devices.

This is very old and I can't reproduce it, and haven't seen any other reports.

See T13602 for eventual followup.

MYSQL_PWD can be observed always

The main problem here is that command "./bin/storage dump" exposes password on system process list in clear text. It happens due to way the storage tool calls mysqldump command. In my opinion this is universally applicable to every Linux distribution Phabricator can run on.

Internally, see also PHI1785.

PHI1776 is another report of this behavior.

This is very old and we have no outstanding customer requests for ARM support.

See also PHI1628, which reports that a 4MB blob of test details is slow to render.

See T13478 for followup.

I'm also still able to reproduce this specific variant of things, so it looks like I was too optimistic about T13462 covering this in at least some cases.

Can confirm this is fixed. Yay!

I believe T13462 resolved this.

I'm going to merge this into T11535 since it's basically the same issue.

See also https://discourse.phabricator-community.org/t/arc-land-fails-with-detached-head/3078/.

This task covers a lot of ground and many of the issues have been resolved. There are two remaining issues which are more narrowly covered by these followups:

This is super old and doesn't have any apparent reproduction instructions.

We've run instances in the Phacility cluster for a long time now, but this is generally not something we really support or plan to support since there's no real customer interest in instancing Phabricator.

This is very old and it doesn't look like we ever found a working set of reproduction steps.

I believe this has been fixed by D20327 / D20393 -- at least, the examples above no longer seem to reproduce any bad behavior.

D20433 deprecates "Track Only", mooting this.

This is effectively mooted by changes in T13277.

See D20419 and T13277.

I marked this as resolved in D20384, since that rewrites this interface and solves this particular issue. The new UI is still fairly rough (thus "v1 Major Jank Edition") and has some new replacement problems, but see T13272 for followups.