Single user can't see profile page

I have one user, who can log in, and do all the normal activities, but if you go to his profile you get:


I tried deleting his user from ./bin/destroy and he was still able to log in! He had to use the normal auth user to get the same result (we use google sso). Only occurs with this one user. I don’t know that I can really call it a bug but if anyone has a suggest next step to try it would be helpful.

He only wanted to change his profile picture…

It’s like bizarro world.

See https://secure.phabricator.com/T13133 for a discussion of what overheating means.

This is fallout from the change in https://secure.phabricator.com/D20294 earlier this year, which made overheating an error by default.

This user account might (for example) be associated with 1,000 recent commits in a repository which the viewers can’t see.

Our behavior here is incorrect; this failure should be contained only to the feed part of the profile. I’ll fix this.

I tried deleting his user from ./bin/destroy and he was still able to log in!

Separately, this is definitely a bug if it’s a reproducible behavior, but it’s hard for me to imagine this isn’t just some kind of confusion/mistake. bin/remove destroy completely DELETEs the corresponding rows from the database:

mysql> select * from user where username = 'betsy'\G
*************************** 1. row ***************************
                        id: 15
                      phid: PHID-USER-6su5u53cdzt5pekqmldm
                  userName: betsy
                  realName: Betsy the Cow
               dateCreated: 1561050483
              dateModified: 1561050483
          profileImagePHID: NULL
        conduitCertificate: 6b7fpzzwakrzbo6ewwi2bsqrf66iekcg4by4kl6uffnnsb57x7ziwfuals5cijl6ttve33s7jez4qkqn6vq7pa4gv5mmci6rwfntldhi7iblp4lrgebyuc5lsnddaxole7x6xyfq34nmxolto3kd52bg4fuklj7rpdsjnzv56dsnu5knhqwthtvd2yeuslt4ifdutccmejfz7qi74pxwjb25exye7i7ixhvgbau4x2xk7oyqud7laacljxejxlh
             isSystemAgent: 0
                isDisabled: 0
                   isAdmin: 0
           isEmailVerified: 0
                isApproved: 1
             accountSecret: pxduphvzibeqgtxbjco66nrrubg23crwmdne6ub7p5pepch56jez5vut2nsbabkx
   isEnrolledInMultiFactor: 0
         availabilityCache: {"until":null,"eventPHID":null,"availability":null}
      availabilityCacheTTL: 1563662723
             isMailingList: 0
   defaultProfileImagePHID: PHID-FILE-bre5ugd5kgpli5y5tglm
defaultProfileImageVersion: v1
1 row in set (0.00 sec)
epriestley@orbital ~/dev/phabricator $ ./bin/remove destroy @betsy


                                  uuuuuuu
                               uu###########uu
                            uu#################uu
                           u#####################u
                          u#######################u
                         u#########################u
                         u#########################u
                         u######"   "###"   "######u
                         "####"      u#u       ####"
                          ###u       u#u       u###
                          ###u      u###u      u###
                           "####uu###   ###uu####"
                            "#######"   "#######"
                              u#######u#######u
                               u#"#"#"#"#"#"#u
                    uuu        ##u# # # # #u##       uuu
                   u####        #####u#u#u###       u####
                    #####uu      "#########"     uu######
                  u###########uu    """""    uuuu##########
                  ####"""##########uuu   uu#########"""###"
                   """      ""###########uu ""#"""
                             uuuu ""##########uuu
                    u###uuu#########uu ""###########uuu###
                    ##########""""           ""###########"
                     "#####"                      ""####""
                       ###"                         ####"


 IMPORTANT  DATA WILL BE PERMANENTLY DESTROYED

Objects will be permanently destroyed. There is no way to undo this operation
or ever retrieve this data unless you maintain external backups.

 IMPORTANT  DELETING OBJECTS OFTEN BREAKS THINGS

Destroying objects may cause related objects to stop working, and may leave
scattered references to objects which no longer exist. In most cases, it is
much better to disable or archive objects instead of destroying them. This
risk is greatest when deleting complex or highly connected objects like
repositories, projects and users.

These tattered edges are an expected consequence of destroying objects, and
the Phabricator upstream will not help you fix them. We strongly recommend
disabling or archiving objects instead.

This object will be destroyed forever:

    - @betsy (PhabricatorUser) betsy (Betsy the Cow)


    Are you absolutely certain you want to destroy this object? [y/N] y

Destroying objects...
Destroying PhabricatorUser @betsy...
Permanently destroyed 1 object.
mysql> select * from user where username = 'betsy'\G
Empty set (0.00 sec)

I filed this upstream as https://secure.phabricator.com/T13349.

This should be fixed by https://secure.phabricator.com/D20678.

There’s also a slightly friendlier description of overheated queries here: https://phurl.io/u/overheated

Thanks! I’ll get this tried out and report back.

The fixed totally worked!