Thanks, little cute Phorge kitten in profile picture <3

Hire someone from the Community seems most optimal for many reasons

Nice, it's a good step towards cleaning up this mess!

It would be nice to have some unit tests for this but that seems like it might be quite a bit of work to implement.

@valerio.bozzolan Proposing to decline in favor of T15940: Update copy of external mimemailparser library / D25829: Update mimemailparser from May 2011 version to 8.0.4.
Let's not increase the diff to upstream (13 years difference) even more.

Confirmed on KDE on Debian 12, everything set to Dutch: LC_ALL evaluates to nl_NL.UTF-8. Fails before applying this change, succeeds afterwards.

I can reproduce this (KDE on Debian 12, everything set to Dutch: LC_ALL evaluates to nl_NL.UTF-8). diff returns localized output, but doesn't when using LC_ALL=C.

Has anybody a terminal with non-English environment and that obtains a non-English output with this command?

Thank you for trying. Let's continue the "how to reproduce" discussion in the bug report T15927

If it's the daemons that are having problems, you can probably see in the /daemons/ dashboard which tasks are causing problems, and narrow it down from there.

ARRRGH, I locally did this on master branch instead of a dedicated branch. Sorry, it's been a while!

For context, the ManiphestTransaction table in my installation has >10mio entries so some charts do not render but time out. One approach could be Materialized Views but I don't see how that's feasible given the "Project" tag parameter coming into play (and having thousands of project tags in my installation), so my vague followup idea for my installation is to completely disable the code which handles the legacy data only (as creating the modern data does not rely on querying the ManiphestTransaction table), and thus deliberately ignore ancient legacy data from before 2018 for the sake of performance. That's easier to achieve when the upstream spaghetti code doesn't constantly switch between handling legacy and modern/synthetic data.

For what it's worth I've applied this to my personal instance which tracks master, and I've foisted it on my work instance too---ostensibly tracking stable there, but ;)

1. Can you add a swap file to allow memory usage above 8gb? This will have poor performance but it may allow repo processing to continue.
2. Can you tell if there is a repo which is still importing? Normal day to day repo tracking shouldn’t require tons of ram so the only situation that I can imagine needing this much ram is importing a large repository.

What is the normal memory usage for the update daemon during the repository update? It seems to be peaking around 8GB per process for our repositories. Maybe I need to add more RAM, i.e. 32 GB to satisfy this, but that's not easy on AWS.

Repository update is based on how recent the last commit is, but that's only for collecting the list of commits to analyze.
But that should be done in the Daemons, which should at least recover nicely and not break the web side of the application. I don't know if they should be running as php or php-fpm.

OK, not the monitoring issue.

@Iniquity - Problem solved by removing that sentence lol - thanks. Now seems super-freshy

Thanks! :)

@BlankEclair Do you want a little help to land this?

@Iniquity - Problem solved by removing that sentence lol - thanks. Now seems super-freshy

Arcanist is misspelled as "Archanist" in the 3rd step of "Updating" section.

Uh! Out of curiosity, what does the notification look like in your web notifications?

Okay, I got it! For future reference if anyone in a similar situation is stumbling across this and wants a fully working example to go off of, my more-than-a-little-cargo-culted code is currently:

Many thanks, @20after4! That all largely did it; in addition to setting up the object a bit wrong (I knew it was a ManiphestTask instance, but was failing to get the actual object of it), I was also just using essentially my:custom-field rather than std:maniphest:my:custom-field.

Appears to be internal monitoring software causing this (not phorge), thanks for the replies.

Noting a user complaint (I'm using a mildly hacked-up Phorge to host https://blog.styx-os.org/ - but the font stack is unchanged): https://fe.disroot.org/objects/5d376f6a-0acc-44fc-bd37-31de8630b647

In T15947#19599, @avivey wrote:

Maybe express it as allowed by Policy xxx? (Related to T15277)

So essentially this:

If I were starting today I would probably design the back-end APIs first, then make the web interface derive from those APIs, such that web requests and api requests are not really any different, at least with regard to enforcing access controls.

Maybe express it as allowed by Policy xxx? (Related to T15277)

No clue :)

P.S. maybe relevant - maybe not :D lol https://we.phorge.it/T15945#19568

This one seems worthy of a rubber stamp. And a gold star.

Are you importing some huge git repo or something? I haven't seen a lot of OOM with php-fpm on phorge/phabricator. It's generally not been an issue in the past so this is either a new bug or something specific to the environment. Then again, I've almost always ran Phorge with much more than 8GB of ram available.

For another example, here is a fairly straightforward use of that API which takes place entirely outside of a custom field subclass:

There is a pretty complicated and not really easy to follow subclass of ManiphestCustomField over here: https://phabricator.wikimedia.org/source/phab-extensions/browse/wmf%252Fstable/src/customfields/ReleaseDetailsCustomField.php

@keithzg what you might be missing is

$object = $this->getObject()

There is a significant amount of Phabricator dark matter out there - companies/people using the software, it works well enough, not really easy to know they exist or anything about their usage. I'm sure at least some of them have moved to Phorge. Automattic/wordpress.com have moved to Phorge and I wasn't even aware that they were using Phabricator before that. This is despite the fact that I did a pretty extensive amount of research to identify every company using Phabricator back in ~2019 as part of my work for Wikimedia, with the goal of reaching out and trying to organize an informal Phabricator users group. We had the idea that the various corporate users probably had good reasons to be collaborating and at least talking to each other since most of them were not active in the upstream project. Anyway, that never really panned out, although it did trigger a flurry of interest and some ongoing discussions via email (maybe even one video meeting but I can't remember the details now.)

Any guess about a supposed right value for service? lol Just for my curiosity

Just talking about accessibility, maybe interesting, Wikipedia on mobile allows to scale, but setting a minimum and maximum scale: