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.

Broader work required than extension/language map update, see T3626.

A better long-term solution than a temporary fix is wanted, per D17104#203911

Stale localisation issue

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

PhabricatorBot is now gone.

PhabricatorBot is now gone.

To package it as a library is a good idea, but code isn't up to date with current Arcanist requirements. See T9316 for more context.

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

PhabricatorProjectWorkboardProfileMenuItem::MENUITEMKEY

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.

Per T10030#150337.

I see D10289 has already offered a similar change.

@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.