This is technically possible (and I believe imported events do have some support for mutation within Phabricator today: for example, I believe you can award them tokens). However, I'm very hesitant to start making imported events writable.

Set mail sender as custom name to edit file externals/phpmailer/class.phpmailer.php, change $this->FromName = $name; to $this->FromName = 'CodeReview';.

I disagree. This option is a lot like email notification options which are already present in Phabricator. It expresses very personal preferences of how user prefers to read the same content. And for me it is more important than ability to set board backgrounds.

See T8227: Why not just add an option/setting/preference?

Hello, here is my use case.

This still needs complete reproduction steps to be accepted into the upstream. My suggestion is find another VM and load out what you expect the issue is with, and give us those details. Right now it sounds like you're just guessing and that's outside of what we expect when following Contributing Bug Reports. See https://secure.phabricator.com/book/phabcontrib/article/reproduction_steps/ if you need more guidance on providing these steps.

In T12521#218608, @chad wrote:

Does this reproduce against a Phacility instance or our test mercurial repository here?

We ultimately built an "ngram index" for this task, see T9979 for discussion.

• T11586 has context.
• D16541 added PHUIInvisibleCharacterView and has usage examples.
• Go hunt down as many error messages which include user input in a validation error as you can find/test and wrap them in PHUIInvisibleCharacterView. The task description lists some. I don't think there's any systematic way to find these, and we shouldn't expect to be exhaustive.
• Close this when satisfied / bored / everything else is too much of a pain to test.
• Primary goal here is just an onboarding goal of poking around some different applications, we haven't really seen users hit this stuff.

• When you click "Delete File", we currently delete the file in the web process. Since we've supported enormous files and pluggable storage backends for a while, this could take an arbitrarily long amount of time to complete.
  • Instead, we want to flag the file as "deleted", hide it in the web UI, and queue up a task in the daemons to actually get rid of the data.

Actually, this will probably take longer to provide guidance for than to implement.

This is now possible with edge.search.

I've been doing production deployments with this for a while without hitting any meaningful issues. It's not general-purpose yet but followups can live in Phage from here on out.

Please indicate the versions of mercurial on client/server as well as any extensions you have enabled on client/server

Use diffusion.repository.search or phid.lookup to map repository identifiers to PHIDs.

Does this reproduce against a Phacility instance or our test mercurial repository here?

I think it does, but only if you ever don't have a profile picture:

Wasn't this supposed to show up as an option in "Edit Profile Picture"?

Late friday night brings good ideas

everytime I type D3 meaning the javascript visualization lib,
it references that Diff #. Similarly with common strings like
#servers looking up projects. I want the auto-linking behavior
most times, I just want a simple escape character for the few
times when I don't.

This is extremely old and doesn't have any use case information, which we require for modern feature requests (see Contributing Feature Requests).

(Just closing this since we haven't seen an update in ~4 months and it isn't actionable.)

This isn't a bug; the cURL request is not a websocket request.

Per the latest update in D17502, this remains involved.

The segfaults appear to have subsided for me so I'm just going to close this as "upgrade to PHP 7.1.2".

While we haven't been showered in free money, I also haven't seen more reports of this so I'm going to presume it's resolved.

I may still do a bit of a UI touchup pass here but this can follow up in T10967, since there's still some other work to be done there (like purging the old double writes).

This appears to now be resolved for me, presumably by the fixes for T12079 and T12219.

I think this got fixed by D17483.

I'm just going to merge this into T8033 since I our intent there is to prevent this situation entirely.

T12335#214054 discusses some future/followup work, but that can be filed separately as it becomes relevant.

From elsewhere, it sounds like this is working.

See "git push = save changes" discussion in T5000.

We don't know how to reproduce this, so we can't move forward.

We don't have any way to move forward here.

We don't know how to reproduce this and can't move forward.

We don't know how to reproduce this.