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.

This is an unconstructive mess that I don't specifically plan to act on. T13069 and other work may eventually resolve this case indirectly.

Currently, expected behavior.

Currently, if a card requires MFA to edit, we're unable to prompt the user. We likely should be able to do a prompt inline. This should also probably have a warning icon on the card itself.

D20196 removes this code.

(I'm not 100% sure that D19972 fixes this completely, but it appeared to locally. In the future, "Mail Stamps" should include this information in a more reliable format, although they do not currently include transaction information. See T13069.)

Presuming something fixed this.

In T12145#242682, @joshuaspence wrote:

I'm having some trouble getting this new behaviour (which IIUC basically means that multiple hosts in a Drydock pool should be load-balanced across). In "active resources" I see three Drydock hosts, which all belong to the same Almanac service. In "active leases", however, I see only a single host lease and many working copy leases.

I'm having some trouble getting this new behaviour (which IIUC basically means that multiple hosts in a Drydock pool should be load-balanced across). In "active resources" I see three Drydock hosts, which all belong to the same Almanac service. In "active leases", however, I see only a single host lease and many working copy leases.

I would like to add another use case where this would be beneficial.

D19762 adds a "supplemental allocation" behavior, which basically lets blueprints say "I want to grow the pool instead of allowing this otherwise valid lease acquisition".

After that, both hosts will have resources and jobs will allocate randomly, which should be good enough.

I believe you can work around this today by disabling the binding to host "A" in Almanac, running one job (which will be forced to allocate on host "B"), then re-enabling the binding. After that, both hosts will have resources and jobs will allocate randomly, which should be good enough. This is exceptionally cumbersome and ridiculous, of course (and it's possible that it doesn't even work).

Well, this sucks... But thank you for taking the time to explain the situation 😃

It's "open" in the sense of Apache-licensed and (mostly) developed in public (e.g., the information on this install is public rather than hidden behind a corporate veil).

@epriestley Does this mean that phabricator isn't open to contributions?

See Planning.

@epriestley
Support for PHPUnit 5.x ended on February 2, 2018.
We need this patch for PHPUnit 6/7 ... any idea when it can be landed on master?

This was almost certainly resolved by D16273.

Changes in T13209 make this the only mode.