It would be nice to make the linter for PHP version symbol issues smarter, so it can detect that if (function_exists('x')) { x(); } is always safe in any PHP version.
A somewhat-adjacent issue to PHI1066 that I hit recently is that more stuff has become Throwable in PHP7.3, and some methods need to transition from Exception to Throwable, like phlog(...). Some Throwable throws result in a blank page today.
(See T13250.) PHI1066 has some possible fallout from query string construction changes.
When an instance is unsuspended, we should automatically schedule a database upgrade. Currently, unsuspending a long-suspended instance tends to lead to a case where the instance is active but missing required schema changes.
D20132 has a followup for adding rate limiting to "Add Payment Method".
D20127 needs a revisit to make it less bad.
See https://discourse.phabricator-community.org/t/configuring-the-number-of-taskmaster-daemons/2394/:
- bin/config set should warn you when a stronger database value exists, and point you toward bin/config delete --database.
- Setup guidance should warn you about locked config with database values, so we can some day stop reading database values from locked config to improve security (e.g., prevent an attacker who bypasses the lock from inserting a value for cluster.mailers which we'll actually respect).
PHI1073 would like to see more task graph nodes.
PHI1051 wants support for overriding custom field behaviors in subtypes. See D17593, previously. This now lives in T13248.
PHI1059 wants stronger edit locks.
PHI912 would like auto-status and auto-submit for Duo.
PHI774 identifies an issue which can likely be mitigated in the short term by improving the "Welcome" flow for non-password installs.
PHI810 would be served by having the Differential "Reviewers" tokenizer to show user availability. Maybe every user tokenizer should do this?
Per PHI810, the "warn when all reviewers are away" in arc should really be "warn when some reviewers are away". We can do this in a coarse way now ("Some reviewers are away: alice, bailey.") and a more nuanced way after toolsets (availaiblity details via user.search).
The left-column alignment of the >> Differential marker is a little weird, and we probably don't need the left-side highlighting on indentation-only lines.
Adding a "Restartable: If Failed" mode to build plans seems reasonable.
PHI896 et al. could really use at least a viability assessment on "does not block draft promotion", etc. See also PHI1093 for "build can not restart".
See PHI1115 for bin/policy unlock --for / --assign. Also, bin/conduit call --as ... may fail on edits while attempting cache rebuilds (EXCEPTION: (PhabricatorDataNotAttachedException) Attempting to access attached data on PhabricatorUser (via getUserSetting()), but the data is not actually attached. Before accessing attachable data on an object, you must load and attach it.).