I just applied the patch to our instance and it works. :) Thanks again. I'll monitor this so I see when I can stop manually applying the patch… ;-)

Oh wow, that was quick, thanks @avivey . I will probably be able to apply the patch to our Phorge instance sometime next week, I'll let you know how it went!

Okay, I think I created a minimal example reproducing the problem. The repository is publicly available here: https://sourceforge.net/p/tinloaf-phorge-problem/code-hg/ci/default/tree/

To be clear - it's a single file in a single commit, in the equivalent of this page: https://we.phorge.it/rARCa604548101025875de20a9c263df3790fea425b3 - is that right?

Our currently running version is git commit 1ba5c8c26095 from 2023-04-20, so that change should already be included. In fact, I can see the --encoding utf8 argument to hg in various logs.

I'm not sure where the buildUpdateFuture() function you linked to is used, but in the stack trace that I see (see previous comment), the future is buit inside executeMercurialUpdate(…), which calls $repository->getRemoteCommandFuture(), which boils down to the call newRemoteCommandEngine(…)->newFuture(); in the repo base class.

In the repo management panel, I see this error:

Raw Error
Error updating working copy: Command failed with error #255!
COMMAND
hg --config ui.ssh=/var/www/phorge/phorge/bin/ssh-connect pull -- '********'

Thanks! I created a Task with the Diffusion tag for it.