The issue doesn't appear in the current code base with Firefox 73. That's not unexpected, as the UI has been tweaked several times between 2015 and now.

I confirm the Maxime Corteel patch to be working with PHPUnit 7.0.1 too.

A quick word to express my satisfaction about the new personal menu: after some days, it becomes standard practice on two instances I use to access current sprint workboard from the menu.

I can repro on an instance upgraded at 20d1bb8fdf too. And indeed PhabricatorProjectWorkboardProfileMenuItem or PhabricatorProfileMenuItem classes don't contain a validateTransactions method.

Reference in PHP 7.1 migration guide: http://php.net/manual/en/migration71.new-features.php#migration71.new-features.asynchronous-signal-handling

Aye, that would allow to visually scan the cards, and to understand what repo is concerned by each change.

The goal is to sort the contributions of one person who committed to a lot of different repositories, to get an overview of where they contribute. For example, that allows me to identify what repos are on my expertise domain so I can review there / who I can contact to unblock situations for other repos.

I've an old generation one. The first three generations weren't U2F.

@ofbeaton For more context and arguments to give if you wish to review your LDAP conventions, see T3167#32426.

I'm not sure this is a problem of Phabricator. It sounds like a problem of your LDAP conventions.

We ultimately want teams to choose different colors so they can know which workboard they're on at a quick glance.

Yes, I concur, that would be useful.

I suspect the goal could be to provide visual hints, in addition to the text, to recognize and disambiguate dashboards.

(2) isn't a solution I'd enjoy, as the feature really helps to gain in productivity. Not to have this means revisit each closed task to assign it.

Let's note this is not an oddball case:

@chad thanks for the clarification, I indeed mangled these authentication tokens with the Tokens application.

@michaeljs1990. You seem to have another issue.

In would be convenient, but note you could have a more generic problem here: how to store all your credentials. Solutions like Vault could help in this case.

To configure the regexp in an .arclint option for the linter seems valuable, with a clear use case.

Indeed, it's directly less helpful in this case.

I can reproduce the issue on a Mercurial repository hosted on Bitbucket: commit imported by Phabricator shows correctly UTF-8 in the diff, but not in the commit message. UTF-8 characters are handled without any issue with Git repos.

Indeed, the mirroring makes more sense.

Thank you. I've tested on a small personal installation, and indeed that works (the repo were configured with git:// URL). That's also really interesting to be able to close the revision directly in the code review app, then be able to directly move to another element of the interface. So, the feature is welcome.

I tried the Land to GitHub feature and got the following issue:

Yes, for the base problem.

I'm taking care of this issue.

@chad I have been more interested by this feature for large open source projects Phabricator instances like the Wikimedia, Blender or FreeBSD ones than for local installs (as they don't met the hundred mails per day volume criteria).

In T6405#82741, @chad wrote:

Even if we implemented, it seems unlikely users would be able to use it on local installs.

Allow rendering Remarkup to text done in D5365.

Well, actually, PhabricatorMetaMTAMail already implements an HTML view.

I don't like the cost to have to add an HTML counterpart to the mail. Even if Gmail will print plain text mail if such preference has been set (I receive my GitHub mails as text) and will still add the notification from the HTML part, it's like an hack. So I'm rather reluctant to the feature.

I concur, the interest is limited, and it clearly belongs to the category of narrow use cases.

@limanoit has added some days later a love token to Q36.

Same issue with any link to Phabricator object, like tasks.

In T5865#10, @chad wrote:

It's actually surprising to me it took this many years for someone to ask for this feature.

The possibility to deinstall macro application (or more easily: simply by not uploading stuff) is probably why it has never been requested.

people who suffer from them will still be tortured by the compact view.

So any image at all, even if small and non-animated, is torturous to you?

Cost/benefit of the "compact" macro view seems pretty low for me:

• people who like animated animated GIF and random picture are okay with the big size.
• people who suffer from them will still be tortured by the compact view.

qqq context documentation is helpful, but not really needed when the translator knows well the software.