That went through totally clean.

I'm going to try truncate + rebuild and see if this is a first-run issue, maybe?

A sub-issue here is that rebuild-identities (and, likewise, CommitMessageParserWorker) uses getAuthorName() from the CommitData.

I did catch a rebuild-identities script eating 66% of CPU this morning, so I'm pretty sure there's a problem there somewhere, but it died at some point (likely when I restarted MySQL?) so there isn't much left in terms of forensic evidence.

My guess is that it's running in a loop and that I have a bug in PhabricatorQueryIterator.

Some of this moved forward into T13151.

I think my plan here is basically:

The "Pending Invites" counter didn't seem to work correctly for this instance.

I never found the time to play any more Bestiary and Incursion just launched. 🐙

Thanks!

In D19455 I've reduced our "enormous change" threshold from 1GB to 256MB, which puts us underneath Git's 512MB magic number. This probably mitigates this to at least some degree.

The companion "provide more guidance" patch would be something like this:

This is involved, and default_authentication_plugin=mysql_native_password doesn't fix it.

When comparing diff 1 to diff 2, hide all files which have not changed [and have no {old/right/undone} inline comments].

An adjacent issue is that the actual connection exception doesn't make it up to setup guidance. It's somewhat tricky to raise it through the stack since the mechanics are substantially delegated to a bunch of cluster connection management, but we should make more of an effort to get it up to top level.

In MySQL 8.0.4: