We have updated to Git 2.11 and updated to master pull/push works for us. Thank you as always. :)

Just tried another and included the full output from arc land and the git merge-base:

The patch didn't appear to work for us.

I noticed that to, they haven't been working for a while. I have been trying to go through the http://marc.info/?l=git mail archive.

We have been having a similar issue. Commits to all repositories are being rejected by the EVIL DRAGON BUREAUCRATS. We upgraded both Phabrictaor (Master) and GIT (2.11.0) as part of the maintenance window. In our setup with host repositiores in Diffusion, using SSH.

We have seen exactly the same error on our instance today, since updating to master. MySQL max_connections was set to the default of 151.

Thank you for the update, I didn't think of using Conference. I haven't found anything that directed me to /status, just had the url as part of our validation after an upgrade, and went to use it.

Following the upgrade, is there a way to send test notifications and /notification/status/ is now a 404 error?

The layouts on secure.phabricator.com appears to be fixed for me

iPad Air2, in landscape (also happens in portrait, just tested)

On mobile, the columns are compressed on the left hand side of the window, and the right hand column of the window is blank, just the grey background (where the durable column would be). Seems to affect all pages so far (homepage, maniphest)

We have been attempting to use conpherence more often, and the real time updates of the threads only seem to work for the first and sometimes second messages, and then stop. There are no errors in the browsers JS console, and other real time notifications appear to be working reliably and do not appear to stop e.g. task/diff updates, reload page popups etc...

@btrahan, the internal 500 error is fixed on both our installs at HEAD. Appreciate the quick response and fix. I'll leave this ticket open as D12347 is marked as fixing this.

Hey,
I have just spun up a new instance of Phabricator using HEAD, and the following allowed me to recreate the error:

Ah ok, for part two, that now makes sense, we didn't realise that was the intention.

In a follow up question to D11990, after we upgraded, the result of the patch for us, using the same use case above, is:

We had a similar experience, set the initial PHID for an image file, didn't like the result and then used the same process to change the image. The PHID changed, but the old file was displayed. I think we found the image was cached in the phabricator_cache database, after clearing those caches the new image displayed.

+1 We have just upgraded Phabricator to head, and get the same error message on almost all commits in all repositories (we have a commit in one repository that was git pushed into the repo and then audited, which will display).