It's not a bug that you can write plans which deadlock.

This is expected. Please read Customizing Forms carefully.

This does not describe a bug in Phabricator. See Contributing Bug Reports for help on filing a valid bug report. See Support Resources for information on getting help with setup and configuration.

• Do T8996 first.
• Add an awarderPHID or similar to the new table and start storing who awarded the badge.
• Render it in the UI somewhere.
• That's good for unbeta, we can add commemorative notes and stuff later. I want to rework the award flow a bit sooner or later anyway.

We want to be able to store metadata about badge awards (like who awarded a badge, when, why, a little commemorative note, etc) but currently can not because they use a very simple storage mechanism (edges). For example, see T8940.

Here's the remaining bug: when a transaction group mixes a comment and another action, badges are not shown, even though we render the profile image in large size and have space to show them. Here's a screenshot of the bug from this task:

To set expectations, this is a very low priority for the upstream. Most prior Asana/JIRA work in this vein has been for paying customers (see Prioritization).

after two users abused this to hide important tasks from developers

You can use arc alias to define some arc pull-then-feature.

I think the fread() thing from PHP.net is just the user being clueless. He's opening a connection to an HTTP server, writing this "HTTP request":

When you have a chance, can anyone else who was hitting this update libphutil/ to rPHU5afd76 and see if it still reproduces?

I'm fairly confident that D14920 will fix this. I was able to reproduce it with the "run in a loop" method, and narrow it down from there.

Yeah, I can't reproduce it anymore either. I definitely saw it earlier today on a different install (which is up-to-date within a couple of hours) but I don't know what was special then.

This is a test.

Jwjsjs

Wjsjsjs

Sjsjdjr

I can't reproduce that. Here's what I did:

Please see Planning. Thanks!

:(

In T9908#148602, @joshuaspence wrote:

It doesn't seem to work properly if I try to comment and also change the status of a task. The comment appears but the task status remains unchanged.

I'm happy to send a diff over, but my design skills are quite lacking. How would.you think that the project tagd should be displayed? For example, suppose that a task is tagged with project X, Y and Z and is being viewed as a worknoard card for the board of project X. I'd say that we should show either Y or Z (as X is implied), but I'm not sure which should be preferred.

Projects displayed on workboard cards. We usually end up doing "[PROJECT] Title" as a workaround.

Is this available for prioritization?

Awesome, glad to hear things sound promising. Thanks for the update!

Ah, thanks! I thought we had one of these floating around.

I can't reproduce this. Here's what I did:

Those reproduction instructions do not describe a bug. When you change a file and add it, it is expected that it will be part of any diffs or commits.

Please include reproduction instructions when filing a bug report. See Contributing Bug Reports.

Ah, I was probably getting confused by that: so as I now understand, the superproject membership inherits from the subprojects it contains?

See T10003. See T9905 for broader discussion. See the Changelog to find information about changes before you perform an upgrade.

Also, adding / removing members from superproject

You can just leave a comment here.

What happens when they try?

Ah, thanks. I think it's just missing a disabled state -- I wouldn't expect the edit to actually go through when you save (or are you seeing the edit work, too?).

6081e640b154631cfc36b4d554a75638201762cd is not a commit in the upstream. Do you have local patches?

This is intentional.

There's nothing particularly actionable remaining here, although we'll always have more things to cache.

No, you can not reorganize existing projects.

I previously linked you to Support Resources. Please read that document.