Change Details

// Queue empty! // --- // Done // See PHI642. An install would like to give "Disable User" permission to all users so everyone can participate in a large "Battle Royale" event. This is an excellent idea but may justify shoring up some aspects of how user accounts are currently edited. This was "mostly done" in Week 33 by T13186. The "Setup Issues" page with no setup issues renders a bit weird: {F5829469} The `auth.require-approval` setting has a non-markup'd link to another setting (note `auth.email-domains`). This would be nice to do somewhat more formally perhaps since I think it's happened a few times? {F5834929} See this beautiful thread: <https://discourse.phabricator-community.org/t/diffusion-differential-mobile-layout-broken-when-enabling-file-tree/1751>. The device reaction logic for filetrees is a bit wonky, and we call a nonexistent `resetdrag()` method. See PHI580. An install would like write API access to object relationships (depends on, fixes, etc). This is complicated, but perhaps plannable, and we may be able to put a reasonable facade with partial support into the upstream. See some prior discussion in T13130. This didn't get much traction previously (see T13137) so the action may just be to punt it for now. (Yeah, I punted this.) See PHI690. An install would like access to Drydock lease metrics, notably the time a lease spent in queue. See also T13073, but this is more narrowly scoped.

See PHI710. This is a request for richer lint/unit results. It's likely entangled with T13088 but can probably be planned. See PHI610. This is yikes. This is also T12251. --- // Done // See PHI642. An install would like to give "Disable User" permission to all users so everyone can participate in a large "Battle Royale" event. This is an excellent idea but may justify shoring up some aspects of how user accounts are currently edited. This was "mostly done" in Week 33 by T13186. The "Setup Issues" page with no setup issues renders a bit weird: {F5829469} The `auth.require-approval` setting has a non-markup'd link to another setting (note `auth.email-domains`). This would be nice to do somewhat more formally perhaps since I think it's happened a few times? {F5834929} See this beautiful thread: <https://discourse.phabricator-community.org/t/diffusion-differential-mobile-layout-broken-when-enabling-file-tree/1751>. The device reaction logic for filetrees is a bit wonky, and we call a nonexistent `resetdrag()` method. See PHI580. An install would like write API access to object relationships (depends on, fixes, etc). This is complicated, but perhaps plannable, and we may be able to put a reasonable facade with partial support into the upstream. See some prior discussion in T13130. This didn't get much traction previously (see T13137) so the action may just be to punt it for now. (Yeah, I punted this.) See PHI690. An install would like access to Drydock lease metrics, notably the time a lease spent in queue. See also T13073, but this is more narrowly scoped.

// Queue empty!See PHI710. This is a request for richer lint/unit results. It's likely entangled with T13088 but can probably be planned. See PHI610. This is yikes. //This is also T12251. --- // Done // See PHI642. An install would like to give "Disable User" permission to all users so everyone can participate in a large "Battle Royale" event. This is an excellent idea but may justify shoring up some aspects of how user accounts are currently edited. This was "mostly done" in Week 33 by T13186. The "Setup Issues" page with no setup issues renders a bit weird: {F5829469} The `auth.require-approval` setting has a non-markup'd link to another setting (note `auth.email-domains`). This would be nice to do somewhat more formally perhaps since I think it's happened a few times? {F5834929} See this beautiful thread: <https://discourse.phabricator-community.org/t/diffusion-differential-mobile-layout-broken-when-enabling-file-tree/1751>. The device reaction logic for filetrees is a bit wonky, and we call a nonexistent `resetdrag()` method. See PHI580. An install would like write API access to object relationships (depends on, fixes, etc). This is complicated, but perhaps plannable, and we may be able to put a reasonable facade with partial support into the upstream. See some prior discussion in T13130. This didn't get much traction previously (see T13137) so the action may just be to punt it for now. (Yeah, I punted this.) See PHI690. An install would like access to Drydock lease metrics, notably the time a lease spent in queue. See also T13073, but this is more narrowly scoped.