3 ms·
So the CEO was a red herring? Just a timing coincidence? I'd love for "the CEO logged in" to be somehow part of the root cause...
by AnimalMuppet 1y ago
So the CEO was a red herring? Just a timing coincidence?
I'd love for "the CEO logged in" to be somehow part of the root cause...
- CableNinja 1y agoActually, i bet they were the cause, and they shouldnt have been. I bet the ceo has some super cow power permissions that let them see every repo, leading to querying the entire db
- cesarb 1y ago> So the CEO was a red herring? Just a timing coincidence? In the code fragment shown on the blog post, the problem would only manifest itself when the "ListUserRepos" call on "ghClient" failed. The CEO account probably lacked some configuration necessary for that call to work (my guess would be that it did not have a valid GH account associated).