+1 the problem is still here. There's no way for a end user to make it right without the need for an admin to go run a command on the server, which is not very good.

The problem here is the default for the default branch, when the user didn't set it explicitly. In a user perspective it's then hard to know there's this option at all. Some link to set the default branch from the error could be more clear, but I don't think that's a common in phab to do that.

Yes, here's the testimony of one of our user,

Thanks a lot, the user should know what he was doing anyway.

I confirm that the task is indeed created with the subproject tag and visible in its workboard when created.

Actually there's a bug with this behavior in the workboard, I can reproduce that in a test instance in phacility as well.

Good catch ! This is a disturbing behavior for the end user though.

+1 it's very confusing

Okay, thank you for the pointers, we have indeed a huge performance improvement using standard mysql replication, which seems to increase the queue usage.

Okay, seems bad indeed, do you think it might explain why the queue is capped at 20-30% ?

Yes, here it is.

Ah yes sorry, I saw some other reference to Nuance today and thought it was for that.

I think you may have answered to the wrong task :)

Hi, we're still strugling with this issue, anybody had to deal with this already ? Is there a plan on optimizing commit parsing and daemons scalability ?

I'm having the same issue since I updated from week 21 to week 27, it happens on empty repositories.

I had to make the admin omnipotent using this trick, but then it had trouble validating the CSRF token.

I've made some modification over this proposition, as suggested it's now using environment variables instead of http headers. I've also ported it to the last version of phabricator and added username autogeneration from first/last names, as my Shibboleth provider give a username that is invalid in Phabricator (numeric_id@institution.tld).