Jarrod and I tried to fix you up as soon as I saw the meta post, saved the investigation for this morning. Let me know if you see anything else odd with your account and I'll get it fixed up.
So what happened was you logged in with another OpenID provider with a verified email address that matched your existing user, this triggers a merge of accounts. A merge is a 2 step operation:
- Merge everything that matters to the master user (posts, name, oldest creation date, etc.)
- Delete the child user which no longer has anything
Deletion is where this one went south, specifically a SQL timeout running in
set DeletionUserId = @comId
where DeletionUserId = @userId
This is a table where flags are stored, when a user is deleted their flags are moved to the community user. In the merge case these were already moved over, but the
.Delete() method is used for regular deletion as well so it runs a few extra things here.
DeletionUserId was not indexed and there was locking on that table at the time, causing your merge to not complete properly (some additional account magic happens after the child user is deleted). The table has grown such that this column just needed an index (yes, when things get big you need indexes for deletes as well as selects!). It shouldn't happen again, for this reason anyway.
Merges can and will fail in other spectacular ways in the future, of this I'm sure. When those crop up, we'll have the same very detailed logging in place to track them down too.