I read the Nuance description, but it is still unclear to me what it does.

Development Log

Development Log

Since this is a relatively large task that's likely to end up with a hundred thousand subtasks, I'll try to summarize progress here periodically.

Oh, and about applications, Maniphest sure, followed by Files, then Mockups, perhaps. Paste... maybe.

The description posted above looks like a good first version.

That sounds like a poor field name for users...

Objects which support spaces get a new "Space:" control on their edit forms.

In concrete terms, major items here that we know about specifically are:

D13024 fixes this for Owners.

Disabled users, unapproved users, and users who have not verified their email addresses may be able to increase their effective permissions by logging out. In some cases, normal users can do this too (if policies have been written which deny them access to resources, but permit public users access).

This is presumably obsoleted by the new scrollbar behavior.

In T4830#74187, @epriestley wrote:

(@btrahan, you're the only repro I have, so don't change your profile picture!)

Cool. D12756 should resolve this in the general case by terminating loops as soon as we try to re-load an object we're already loading.

Deleting the rows resolved all the issues in T8119: Strange behaviour (possibly infinite recursion) on feeds and tasks.

The query is order by dateCreated desc, so technically they're last. :)

Yep, should be safe (although the first two rows are probably the issue?).

@epriestley, is it safe to just delete these last two rows?

Definitely my problem:

MariaDB [phabricator_file]> select * from edge order by dateCreated desc limit 5;
+--------------------------------+------+--------------------------------+-------------+-----+--------+
| src                            | type | dst                            | dateCreated | seq | dataID |
+--------------------------------+------+--------------------------------+-------------+-----+--------+
| PHID-FILE-qffup4ki3h7houulve3d |   26 | PHID-FILE-qffup4ki3h7houulve3d |  1430992455 |   1 |   NULL |
| PHID-FILE-qffup4ki3h7houulve3d |   25 | PHID-FILE-qffup4ki3h7houulve3d |  1430992455 |   0 |   NULL |
| PHID-FILE-qffup4ki3h7houulve3d |   21 | PHID-USER-j4owr5kdhj243qlkhu6l |  1430992319 |   0 |   NULL |
| PHID-FILE-qffup4ki3h7houulve3d |   26 | PHID-TASK-mirzruisn77tw4zow52a |  1430991972 |   0 |   NULL |
| PHID-FILE-7oogy4flcolzbmxzoqy7 |   26 | PHID-TASK-aktaetetss24d24lnzsu |  1430930202 |   0 |   NULL |
+--------------------------------+------+--------------------------------+-------------+-----+--------+
5 rows in set (0.00 sec)

T8119 hit this in a non-theoretical way.

I think that use case is quite different: spaces provides some very high level isolation between various groups of users. These uses cases relate to projects/tasks/etc. within the same space.

T3820 is the main task you'll want to follow. I don't think we'd be likely to pursue any of these until we understand if they're needed after Spaces.

There are a few problems or use cases that would be solved by this:

Please describe the problem you are having in Phabricator.

It should setDisabled() + setWorkflow(); the former will grey it out (T7507 already had that part). Overall behavior should be the same.

Assuming that we want the same behavior as T7507: Should return to previous page after clicking "OK", not actually greying anything out?

Perhaps obvious but things like a "Join" policy, User create policy, etc should render correctly too. Anything that inherits PhabricatorPolicyCapability is fair game.

See-Also: https://phabricator.wikimedia.org/T493

This seems structurally correct but is a lot of work.