OK thanks! you persuaded me

LC_ALL=C is not risky on GNU systems.

A bit more than Normal, since it reflects on a database with orphan elements that creates "ghosts in the UI".

Probably OK now

Relevant old upstream comment (from an unrelated task) that describes this problem as "ghosts in the UI":

git config --global core.quotepath false

Posted question at git@vger.kernel.org.

I also faced this, tested @ D25623, and found out git format-patch was emitting that result which causes git apply to fail. See this git format-patch example.

I can reproduce but the title is so generic that makes this not actionable.

That's because we applied D25415

Cannot reproduce anymore / fixed?

Thanks again :) Giving right credits

Can't reproduce either - 🤷🏻‍♂️

@avivey hi!
I cant reproduce it. Is the problem still there?

Yeah, that might help (like specifically in the case of the Clone dialog) even though it wouldn't help with dialogs containing writable inputs. (E.g. on the repository page, click Flag For Later instead and press Shift+Tab and Escape.) A better fix would lie at https://we.phorge.it/source/phorge/browse/master/webroot/rsrc/externals/javelin/lib/Workflow.js$413 where either the getSpecialKey would need improvement itself to return true for these non-modifying keys, or it would need to be amended with a custom check in that regard. However, I don't know where that function comes from.

Probably something here should be expanded to check if the form contains at least a visible input without read-only

done...

Yeah, probably. I'll try to do it tonight.

Can this (I mean rPb445e1d80df9 )be backported into stable?

I can reproduce this, on an hosted Subversion repository.

It might not happen on any other card, because we might not be rendering Remarkup on any other card. Interesting....

So this is quite an edge-case:

• PhabricatorMentionRemarkupRule wants to give the mention a different color, depending on if the user can view the "context object", in this case the Project.
• There's an automatic rule, saying a member of a project can always view the project
• When loading the project for the hovercard, we don't bother loading all the member list
• When loading the user for the mention, we don't bother loading all its projects
• so data is not available at the rendering point.