OK. Well, thaanks \o/

In T15872#18251, @valerio.bozzolan wrote:

About this:

unset LC_ALL + LC_MESSAGES=C

I think it's not safe since other LC_STUFF can still be read 🤔

About this:

This [LANG=C] is supposed to be the default for missing LC_stuff

OK thanks! you persuaded me

LC_ALL=C is not risky on GNU systems.

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.

In T15096#12185, @valerio.bozzolan wrote:

Another problem dramatically frequent for newcomers (at least in my office).

It's relatively too much easy to start with a similar commit message:
...

At least, please go to GitLab, instead of GitHub, so at least you use Free Software :)

Just some (probably final) thoughts on arcanist and phabricator/phorge. After quite a bit of discussion internally, we are moving on to GitHub with our repositories (which were previously stored in another Git server - not Phabricator). But that move also spells the end for our/my 10+ year long use of Phabricator, because when we move to GitHub, we'll also be ditching Phabricator for code reviews.

Since Subversion allows to checkout just a sub-directory,

Maybe we can wontfix this, and try other more modern approaches like flatpak. Example:

6 year old in-your-face unreported bugs like these make me wonder how many people use Phabricator/Phorge :-(

It's not many, but this issue would be specific to anyone using Phabricator/Phorge for PHP development, which is likely Phab/Phorge itself is close to 100% of that market. And Phab/Phorge also itself has its own unit testing framework instead of PHPUnit.

As an aside, what do you think of https://github.com/campbsb/example-phorge-php-project - should we put a selection of example projects on https://we.phorge.it, either as individual repos, or one repo containing a bunch of examples, or somewhere in the arcanist repo ?

More complete test case added to D25472 which demonstrates the following error:

In T15667#14211, @Sten wrote:

how many people use Phabricator/Phorge :-(

I guess the documentation needs an update on page https://we.phorge.it/book/phorge/article/arcanist_lint_unit/ and/or https://we.phorge.it/book/phorge/article/arcanist_new_project/

6 year old in-your-face unreported bugs like these make me wonder how many people use Phabricator/Phorge :-(

Nix

Just for my curiosity, what lovely package are you crafting? APT? snap? Thanks :)

Another problem dramatically frequent for newcomers (at least in my office).

See https://we.phorge.it/T15533#11839 - the env-selecting code in ExecFuture has this logic:

Hi @speck are you still a Mercurial user? Does arc browse <file> work for you? Just for my curiosity

It is on Diffusion > My repository > Selected commit SHA diff page. E.g. https://<domain>/R1:abdcdefgh

I've extracted T15535: Using Differential with plain Git, without requiring Arc for the git-push-for-revision.

In T15096#11546, @avivey wrote:

Interesting.... Herald could probably start the flow, but there's still more parts needed (update vs create revision, extract summary and test plan)

Has anyone experimented with using arcanist in a docker container? I see two people have published these on dockerhub:

• https://hub.docker.com/r/nasqueron/arcanist
• https://hub.docker.com/r/adlogix/arcanist

Where exactly are you seeing this error? what page exactly?

Interesting.... Herald could probably start the flow, but there's still more parts needed (update vs create revision, extract summary and test plan), and it technically can't delete the branch (it can prevent it from being created, but that shows up as an error in the user-side).
But it should be able to at least trigger the flow and provide a URL for the user to click on.

Could this be solved with a Herald action?

I suspect there's also a problem of motivation: These things are lots of work, and the people who are capable of performing them - people who are comfortable with working with these tools - will not personally benefit from this stuff. The people who would benefit the most are people who are not involved in the project at all...

I think the current actionable steps we can take are: