You can remove the prefix with metamta.differential.subject-prefix, and remove the action with metamta.vary-subjects, but both of these will also affect mail.

Oh, you're translating Audit. That's why it says "Accept Commit". I thought you were translating Differential, sorry. Everything else should work in Audit.

• JSON does not use "\x" escapes. See https://json.org/
• The untranslated text is "Accept Revision ✔", I'm not sure why yours says "Accept Commit ✔".
• This config value:

rPf5ff10fe28 added better tools for smaller Remarkup areas. Please update Phabricator.

Devices:

• Galaxy Note 4, Chrome, Android 4.4.4 2560x1440
• Sony Xperia Z2, Android 5.1.1, 1920x1080

Great, it works like a charm !

@cspeckmim - you're right. But for now I'm not going to create Maniphest Task because I'm a novice in Phabricator. Actually I don't think, but maybe I did wrong something. Before writing this question I've seen T9450. When I become a more experienced user, I'll use Maniphest tasks. Thanks for your advice and sharing your experiences.

Yeah, the Q&A section isn't monitored for these kinds of things, it's more for support.
However, since this is hard to reproduce (See Contributing Bug Reports), it would be very hard to get any resources to solve.

@efkan - you should probably make a Maniphest Task for errors you run into rather than a Ponder Question - errors will likely be seen and fixed sooner than questions. For example I am not an administrator and I don't believe @avivey is either (but a very active user/contributor).

This issue had been created for to create awareness to administrators and users.

It's late...

The mercurial server is sending down capabilities which includes bundle2 at the beginning of the remote SSH during push (which tells the client it can use new bundle2). It's not sent as part of a command which the client invokes which is what T9450 is handling. Instead when the mercurial command server initializes it immediately sends over a list of capabilities.

I think I may see what the issue is. I believe the 'hello' command returns its list of capabilities, which is not filtered by T9450. I'm trying to test out some fixes but having difficulty with nano~

I can confirm this as well. (I also tried to find where this was to fix it...couldn't locate it. @epriestley, if you point me to the file this bug would be coming from, I'd love to tackle this.)

Ah, I just edited because I realized the difference b/w hashtag and title. I don't like punctuation in hashtags anyway, so all's well. :)

Parens?

To clarify, you can put anything you want in a project name. Only hashtags have character restrictions. ??? Whales! ??? ~(BIG WHALES)~ is a completely legitimate project name, and will be forever.

The icon is the fullscreen editor.

It should look like this:

Actually, the fullscreen icon is visible for me in tablet mode. @mna is your Phabricator up to date?

Phabricator is responsively designed for three common breakpoints: Phone, tablet, and desktop. It doesn't make much sense to get more nuanced than that, and some edge cases (like wide phones or narrow tablets) might not work perfectly.

I don't mind DCing use of [] in the title, if that's what you were saying we should do...forgive me if I misunderstood. If so, I need something to use as a replacement. We have projects that are Teams, Projects, Departments, and Groups, all which need to be easily queried, and all of which need to be obvious where they belong. Right now, I'm saying "IMF [Team]", "PawLIB [Project]", and so forth. Just saying "IMF Team" or "PawLIB Project" looks entirely too messy and disorganized for our use.

It looks like they are in tablet layout, since the phone is in landscape mode.

You can now add links to wiki pages, conpherences, etc., to the sidebar.

Specifically, the issue was that these commits contained strings like R2/R13, which the parser was getting confused about because of an improperly grouped regular expression.

This should be fixed by D15049. Thanks for the detailed reproduction instructions, including a repository I could clone locally.

What device are you using, and what is the screen resolution of your device?

• D15045 fixes the problem with "Additional Hashtags" getting smushed.
• D15048 fixes a problem where removing old, invalid "Additional Hashtags" could fail.
• D15047 should fix old hashtags 404'ing.

I'm hitting the same problem using Chrome (Version 41.0.2272.89 (64-bit)).
However when using firefox, I do not have this problem so it seems to be browser related.

The mitigation was applied to remaining nodes on Jan 16, and everything was also upgraded to OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.4, OpenSSL 1.0.1f 6 Jan 2014, which is the Ubuntu upstream fix for the issue.

If the acceptation of only one blocking reviewer among all of them is enough to consider the revision as accepted, I don't need this feature anymore.

Presuming resolved by D15030.

I cloned Phabricator on 2016-01-16 by using that. Because of I use Windows OS, I cannot run arc upgrade.

I use ubuntu 14.04.2 as my server and its hg version is 3.3.2.
I had upgraded when I couldn't push to the server.

This would be a useful feature as well for myself and the rest of my team. We also find the local commits quite useful.
Please add support to have each local commit translate into a revision update, as suggested at the top of the thread. That would be fantastic.

I just tried pushing a commit and this worked fine. I tried this with 3.6.3 on the client and tried pushing commits with these different versions on the server:

• 2.6.2
• 3.4.2
• 3.5.1
• 3.6.3

In every case the push when through without issues. I suspect @efkan may have an outdated install/configuration.

I'm guessing this is still years (or decades) away on the road map, but we want to be able to run build agents in the us-west-2 region and our Phabricator cluster currently resides in ap-southeast-2. Having a way of replication repositories across AWS regions (by setting up Phabricator cluster instances in us-west-2 and having the repositories replicate over to them) would be very useful in terms of reducing our git clone times.

Also having this issue on our install on all projects with characters like (, ), and *

What's the hg version on the server?

If I switch the setting to ["http","https","mailto","hyper","itms-services"], then the exception is gone. So I guess the format is a JSON array, not object. But like I said above, hyperlinks don't work at all.

Ah and when I attempt to save the doc, I get this error:

Unhandled Exception ("InvalidArgumentException")

Still doesn't seem to work: all links are broken in Phriction:

{ "http": true, "https": true, "mailto": true, "tel": true }