Can you show me the complete output on the client with --trace?

Pretty sure this is fixed now, let me know if you're still seeing it at HEAD.

I think they could probably be like 1/2 or 1/3 the size they currently are and still get the point across, maybe.

(This might have some bugs or whatever, idk.)

That's it, I'm all out of "Participant" badges. Sorry if you missed this exciting, limited-time badge!

Is arc up to date? This change affects Arcanist, not Phabricator.

Broadly, this is messy because:

Let me see if I can give you a skeleton for it.

I will get to it eventually but realistically I haven't started doing anything here. Feel free to reassign.

I've decommissioned the old secure.phabricator.com host.

We aren't able to reproduce this.

64c877702 is about 3 months out of date (April 29).

Rolling.

@devurandom, see {I4} if you'd like a personalized status update on this task.

I can't reproduce this.

It sounds like you actually want T731.

We only convey this information through the use of color, which could also cause difficulty for users who do have vision problems.

https://secure.phabricator.com/book/phabcontrib/article/feature_requests/#describe-problems

Sorry, I've only got these "Participant" badges.

I've seen this a bunch of times.

In T8943#127919, @chad wrote:

I think you misunderstand what Badges are for.

Happy to accept a diff for this whenever anyone gets around to it.

If the \\ fix above doesn't resolve it, the fix is probably fiddling with the regexps in PhutilConsoleFormatter::formatString(), but I'm not sure how they're misfiring since they work correctly on my machine and I don't see anything ambiguous in the construction.

In phutil_console_format(), we convert ##xyz## to inverted text, but the \ present in the input is intended to prevent this.

I spent 3 seconds on this, but the location where the error occurs and the locations where we know which error message to print are somewhat distant from one another so disentangling this will take a bit of work.

Thanks!

Cool. Let us know if you're still having issues.

It is always English (US).

You can use bin/policy unlock <object> to open up the policies on an object. For example, bin/policy unlock rXYZ.

Pretty sure this was fixed by D13519.