I'm at 236253df8cd69a3c7d3da984bd2f1837e92330cc

Got the same issue / callstack as @nochum after today upgrade, which was fine (especially storage upgrade)

You can enforce the setting in /etc/security/limits.d/<user>.conf, example :

<user> hard nofile 8192
<user> soft nofile 8192

Replace <user> with the service username

Issue was: no more disk space

Just had this issue today on our mercurial repository. Exact same exception when executing ./bin/repository update --trace <repository>
I've managed to solve it.

I was at the following version:

• phabricator: 4ab9ebd9013aa4bd561aa8c575e167b9fb66d0b3
• libphutil: efc338d50f17dec594a66337034797c90c8b10c1

ping

Hello,
Thanks for the quick answer.

@cspeckmim it works but only by :

• adding a bookmark to the latest commit in the review
• adding a bookmark for the most recent commit in default, which is useless (There's always only 1 head for defaultbranch on the repo i'm pushing).
• using --squash

I still have the issue, even when upgrading Phabricator.

I'm using mercurial and it's painful to watch arc land fail when using anonymous branches.
An anonymous branch is a mercurial basic concept: you can have multiple heads for the same branch name.
Here: 13945 and 139647+ are both heads in "default" branch.

Ok, thanks.
The 12:xy AM syntax is a little confusing for an european used to 24H format.

Well actually it's the same exception, the message was slightly changed ~26 days ago, see rPHU0135e57181a91e1f342338d62782754e0bd31e59
Ok so let's sum this up:

Looks similar to T6433, which is fixed by T6350.
Tried to upgrade, but nope still the same issue.

Got the very same issue over here.

Found the root cause!

Tried with a third and clean windows : working nicely.

Same error on another computer, but this time with several incorrect chars ♀♀?