At the lowest levels:

This needs a lot more work, but here's very roughly where I'm trying to go with this:

D20808 fixes the two original cases (Harbormaster and Legalpad). There are probably more fields or actions which could be configured to be sometimes-unavailable, but these are probably the major ones.

For LDAP, brew install openldap + --with-ldap=/usr/local/opt/openldap/.

Here's the fate of the various issues discussed here:

This should be reworked some day (perhaps partly here) into some more cohesive API, perhaps newLink().

One other thing is that PhabricatorApplicationPolicyChangeTransaction->renderApplicationPolicy() has unconventional behaviors which are not very helpful and not consistent with normal CAN_EDIT / CAN_VIEW transactions. This is somewhat perplexing because ModularTransactions has renderPolicy() already, which has better behavior. I think it didn't exist yet when Applications modularized in D17757, and when it was introduced in D19829 I just overlooked the opportunity to update it.

In Applications → (Pick Something), if an application policy is set to "Custom Policy", the policy is not linked.

I upstreamed this to Chrome here: https://bugs.chromium.org/p/chromium/issues/detail?id=1003002

0.00000000001 is very funny and we would be losing a truly great joke at such a young age

Left Nav

There may also be no Application in contexts where we want to render a global search menu, notably the 404 page:

Vaguely adjacent:

I think I missed one case here: the global preference will currently show custom personal queries for the viewing user, but selecting these queries won't work (at least, not completely) for other users. Instead, the control should offer only hard-coded options and global queries.

But did you check your spam folder? 😄

I attempted to register for a developer account and am receiving neither an email verification email nor a password reset email. 🤷

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

Our behavior appears to be correct when the load balancer is an AWS ELB.

There are only 23 occurrences of the string "GROUP BY" in the codebase, and, from inspection, many obviously do not conflict with ONLY_FULL_GROUP_BY.

Also remaining is to extend this behavior to the HTTP pathway (and to Mercurial/SVN, eventually).