First pass, these one do not apply to us (and some of them do not apply to anyone at all):

(I've put a note in Dependencies for now)

I guess we could also try to cache the individual rendered code-blocks.

(and I made sure this new function isn't exported to the arc lib namespace)

extract to function

Yeah, it's probably not impossible to so safely - especially since people has been working on it for over a decade - but it's hard to do right. I know Wikipedia allows user-uploaded SVGs in some way, so maybe this is a solved problem.

I fixed arc test-traits in R12 (45f900a587).

Update: I've installed pygments (2.15.1), and it took about 3 seconds to render. It takes about 14 seconds here (with pygments 2.3.1).

mm, dumping this file in my dev env renders pretty much immediately; that's a good sign that it's the code blocks, because (1) pygments is known to be slow and (2) I don't have it installed.

"slow remarkup" often boils down to 1-2 inefficient regexp in a rule somewhere.

In D25051#15888, @valerio.bozzolan wrote:

I'm a little worried about this migration; Do we have garbage collector for this? it would be safer to let it run.

You are concerned for performance reasons because it doesn't limit the results. Right?

Looks good to me. @speck

Look into the "is creation xaction" - we had a similar diff recently about creating Revision from raw diff that had a similar behavior.

Also, maybe combine with the ArcanistXUnitTestResultParser.

So maybe rename the parser to JUnitTestResult, or something like that (If that's the right name for the format and if phpunit is using the same format)?

1. (Yes, arc liberate --clean. I'll also run it in Phorge).
2. I'll check it again, I refactored some things and maybe I broke that.

Yeah, in this one special place it doesn't matter; But that page already have a special body, so we can save even the extra click by putting the message right there...

But in Diffusion, that button is hidden behind a "Actions -> Manage" button, inside a screen that also has dozens of other admin actions. The clutter cost there is minimized.

In that case, we don't even need another button - just add a line to the "deleted message" that says something like "To completely remove the history from the database, contact your admin".

I feel that adding such a button would clutter the UI.
Users should generally "know" that in order to really delete things, they need to go to the admin, because they don't have the permissions anyway; And adding that just for the once-in-a-while that the admin needs this...

I don't think we actually allow "deleting" from the web ui, only hiding it (in the sense that the data is not removed from the database).

It also effects the PhabricatorCustomField::ROLE_APPLICATIONSEARCH condition, and possibly actually storing the data in some search-able table.
But try other roles - maybe it will work anyway.

move }

lint

Here's what it looks like with all the bells:

small fix

So after working on this for a day or so, and making much progress, I found that I already built this once 🤦‍♂️
https://secure.phabricator.com/D17004

I think we already did - @valerio.bozzolan ?

It's a Phacility server, managed at https://secure.phabricator.com/phurl/

I've looked down some of the links of this request, and it looks like the definition of "new user" should be install-specific, and open to interpretation.

I changed my mind again. No need for edges (short story is, getting the "color" property from the edge is annoying).

Yeah, I don't like the diviner page.
For other included 3rd parties, we often put a license file right next to the asset:

• https://we.phorge.it/source/phorge/browse/master/webroot/rsrc/externals/font/lato/LICENSE.txt
• https://we.phorge.it/source/phorge/browse/master/webroot/rsrc/externals/d3/LICENSE
• https://we.phorge.it/source/phorge/browse/master/externals/mimemailparser/LICENSE
• and, https://we.phorge.it/source/phorge/browse/master/externals/octicons/LICENSE which is not next to the actual content.

This was both harder and easier then I expected. I got to crash the IDE and hard-code a bunch of stuff, but this actually works. Didn't even start on the Edges implementation yet - I'm directly using the Flags table.

We can probably add a checkbox, and some nicer handling for the exception. Or possibly, just adding the word "regex" might solve this from the "user expectation" side.

The word "pattern" was meant to imply "regex pattern".
Specifically - the ability to search for a regex is much more useful then a plain-text only search (and costs us basically nothing).

Ok, see here: https://we.phorge.it/book/phorge/article/configuring_outbound_email/#outbound-quot-from-quot-and-quot

btw, for the "search" use-case I'm describing, I'm imagining something like a Function on Users/project, so I can search, for example "Tasks that are assigned to users which I flagged with a green flag" or "Tasks that have a tag that I flagged with a blue flag".
And also, "Revisions that I flagged with any flag".

I looked into this again.