T4027 is another case of commits titled [JIRA-123] Blah blah blah.

This is very old, possibly fixed by now, doesn't include reproduction steps, and other users haven't reported issues. If you have specific issues with externals and reproduction steps, feel free to file new tasks.

This is extremely old and I think no longer relevant. The crumbs now show the current branch, and I think Diffusion got better about consistently showing and retaining branches.

T5744 mentions another narrower and more reasonable use case (get specific badness which matches some pattern fixed), which is similar to the Mochi/i18n stuff.

T5046 has a specific case of this causing particularly questionable behavior when doing HTTP clones -- since the object is totally hidden, you don't get prompted for credentials.

This is expected with Spaces, which completely hide objects (primarily as a performance consideration). I'm going to merge this into T9771 which discusses this issue more broadly.

T8296 is a similar case for "Add Mirror".

This behavior is not expected. Please file a bug report with reproduction instructions.

Thanks for the report! Let us know if you run into anything else.

See the documentation: sh -c `some subcommand`

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.

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

Please see Planning. Thanks!

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

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