[scale up] Repos without pytorch-bot installed will not have scaleUpChron

[clee2000]

As in title.

Specific example being meta-pytorch/torchcodec, which had queueing https://fb.workplace.com/groups/4571909969591489/posts/24746420008380521
on October 1 ~8am

scaleUpChron doesn't realize since it queries HUD, which uses ClickHouse data, which relies on pytorch-bot being installed on the repo, which it doesn't appear to be for torchcodec

We can install the bot on torchcodec (I think it used to be installed when it was in the pytorch org, I see some entries in the table from pytorch/torchcodec), but this is more of a general issue for other repos that might not want to install the bot but still want scaleUpChron (ex if a repo wants to remain private/is not ready to be published, installing pytorch-bot will expose it HUD, which might not be good)

[malfet]

@clee2000 semi-volunteered to look into this one, but IMO it's important to have working scaleup for meta-pytorch

Is there a harm in having 1-2 instances of each type to always be there?

[clee2000]

I have installed pytorch-bot on torchcodec so it'll show up in the query for queued jobs