Confirming that the patch above works (tested using send-test --to)!

See Planning

What happened with Phrequent Prototype?
We are looking for a time tracking plugin for Phabircator as well. Is there any plan to have one integrated at some point?

Then, I will use the WMF extension for now. I understand that you won't prioritize this. Just for future reference, I will document the structure we have come up with : I currently employ already a more hierarchical project/subproject structure that can be use over several semesters and makes it possible for me to reference all students at once:

Old-school resigns, accepts, and rejects are still using edges directly (can we get rid of these completely?).

These pathways are still dodging ModularTransactions and thus not getting double writes after D17495:

Specifically, from the error, since X and Y are consistent in the error part and the fetch part, it appears that this process has lost a race to another process which is doing the same fetch.

For now, "Edit Menu" on your home, click "Global" and add the Dashboard. "Default" is the topmost dashboard. You can disable "Home" then. This will be easier after D17492 lands.

How exactly is this currently possible? I am trying to change the default homepage for all users but not managing to do that. Have tried creating a Dashboard, but not sure how I can use that to 'replace' the homepage for everyone.

(Presuming this is resolved since it's been open for a while without feedback.)

Feel free to file a new report if you are able to come up with clear, working reproduction steps that reproduce this issue on a clean install.

Some workarounds in the short term:

This is likely just some of the secure hosts having different configuration. Ideally, we'd get the rCORE deployment stuff aligned to deploy them with it.

We may eventually build this for T7413 but I don't think it's a good use of our time without a strong, narrow motivating use case like that.

This doesn't appear to be moving toward becoming an actionable report.

Any ideas on how we can move forward with this?

These CSS rules:

OK weird, I can't reproduce it anymore. Anyway, I'll add the response body from differential.querydiffs here. It shouldn't contain any sensitive information, but I'll restrict the visibility of the file given that it does contain email addresses.

rLOCATIONS now has two branches:

Sorry, we don't take bug reports as support requests. Have you read and followed Contributing Bug Reports?

Please let us know if we have missed out any settings.

After installing the phabricator we created a new repository.

When the repository is in inactive state the "ssh git clone...." of the repository is shown up.
When we activate the repository and try to see the repository mail screen, the below error is showing up.

Bug reports need complete reproduction instructions and complete version information. See Contributing Bug Reports, Providing Reproduction Steps, and Providing Version Information.

(You can use T12270 to give feedback or report bugs on Badges, specifically)

Please read and follow Contributing Bug Reports. Also, we don't accept bug reports against prototype applications.

Yes, it is not "incorrect" but it is not human-readable format problem same with T8973 either. Chinese / Japanese / Korean unicode should be shown as what it is instead of some unreadable unicode digitals, especially in TRANSLATION functions, otherwise how to translate and confirm that?

Did you try to enable PHP's error logging to get more output?

That's the big problem, the logs say nothing.

Bug reports need complete reproduction instructions and complete version information. See Contributing Bug Reports, Providing Reproduction Steps, and Providing Version Information.

Tried again with node v6.9.4 (current version of node with CentOS7), and still has same problem 😢

Happy to accept a patch for this (deleting that one line of code) if someone wants to claim that they tested the scenario above and it worked correctly.

This behavior is not "incorrect", it just isn't the most human-readable format we could use. I'm going to merge this into T8973, which discusses this and other potential improvements to human-readability for JSON encoded for presentation.

You can award and revoke badges from conduit, though we may build a more robust award api later.

👍🏼

When I checked the source code I saw that the anchor tag was being applied
to the profile image, so I assumed that the link should be clickable only
inside the area of the profile image.

Why do you think its a bug?

Yes, I was referring to a small area around the hovercard which was clickable. Not a big issue, but just something I noticed the other day. 😄

Great, thank you!

T7413 is security/usage data.

After D17489 you should be able to do this:

Sounds reasonable to me.

Hrrm -- I can adjust bin/mail send-test to accept raw email addresses, and then you can use it to send a message to test+00001@gmail.com, test+00002@gmail.com and similar. Shouldn't be too involved.