Could someone create a Mercurial bug (https://bz.mercurial-scm.org) with explanation about how Phabricator handles the bundle2 ssh stream? They might be able to give some hints.
I would like to do it, but I'm not sure how Phabricator handles the stream exactly.

In T9807#144874, @epriestley wrote:

If you want to test that something in this vein works, I'm happy to bring it upstream.

Thanks, I guess that's the best fix in the short-term. I've also tried implementing the bundle2 protocol, but no luck. Without any documentation it's no fun.

Right, sometimes it works perfectly. I just don't get it, it seems kinda random. Maybe I should try once more on another new VM. Please note it only happens when there were commits to push. Pushing without changes always works.

This is my latest debugging result:

I've installed Phabricator on a freshly installed server and switched to Mercurial over SSH. Now I'm getting the same problem, but it's kinda random somehow. Sometimes I don't get the error, but most of the times I do:

Thanks, I'll also try to play with it the coming week. What's the best way to debug PHP? Is there a way to get a CLI debugger at that point of the code or should I just try to print vars to stdout or something? (not much PHP experience).

In T9450#137728, @cspeckmim wrote:

I setup a test environment with mercurial 3.5.1 on both client and server and did not see this issue. Provide some further detail about your setup:

That's weird, I'll investigate it further.

Im using 3.5.1 on both the server and the client. It only happens if I push to the mercurial repos via Phabricator, directly works fine. So maybe Phabricator is not passing through some information needed by Mercurial?