[Upstream Issue] GitHub Stats Card broken for some usernames

[rickstaa]

Describe the bug

Since 2 days the Github Stats Card on my personal README.md appears to be broken when my username is used. When I switch the username to another user, for example, anuraghazra the card starts to work again. Switching from my self-hosted vercel instance to the community one does not solve the issue. All the other cards seem to work fine with my GitHub username. The only error GitHub gives me is the following:

Error Fetching Resource

Might be something I have to sort out with the GitHub support, but I first wanted to check if somebody else is also experiencing this issue.

Expected behaviour

I would expect that the card also works for my username.

Screenshots / Live demo link (paste the github-readme-stats link as markdown image)

Additional info

I currently use #1122 to also receive organization stats, but the issue also appears on the master branch.

[Zethson]

Also happens to me.

[fzyzcjy]

Same issue here.

[JohannesKlauss]

Also happens to me.

[rickstaa]

Thanks for letting me know that I'm not the only one with this problem! Maybe from now, let's add a thumbs up instead of commenting when you don't have additional information relating to this bug. This will keep this issue and our mailbox clutter-free :).

[anuraghazra]

Okay I don't think this is from our end.

Something is really messed up from github's side.

It's returning error/HTML content on graphql api request

Note that it's only happening for few users.

[rickstaa]

@anuraghazra Thanks for investigating this issue. It is strange that it does only happen for certain usernames. When I use your username, for example, the GitHub Stats Card works fine. The API appears to be online (see https://www.githubstatus.com/). I will create a ticket with the GitHub support.

[anuraghazra]

Yes, it's weird! only happens with few usernames. Sure thanks, you can report to them only they can fix this.

Also collect all the usernames which are failing.. see #1405 too.

[rickstaa]

@anuraghazra I will make a list of the usernames that fail. In the meantime, I think I found the field that breaks the GraphQL API. The HTTPS error is thrown when you try to request the following field:

issues(first: 1) {
    totalCount
}

All the other fields work fine. You can test it out by using the following request in the graphql explorer:

{
  viewer {
    name
    login
    issues(first: 1) {
      totalCount
    }
  }
}

Could it be that certain users have too many issues, and it times out? I will add it to the ticket.

[rickstaa]

@anuraghazra are you sure the syntax is correct maybe there was an API change. I checked https://docs.github.com/en/graphql/overview/breaking-changes but could not find one. I use the following it appears to work:

issues(states:OPEN) {
    totalCount
}

But if this is the cause it is strange that it only happens for certain usernames.

[anuraghazra]

Oh cool! nice find.

But still seems there's something wrong with their APIs.

Could it be that certain users have too many issues, and it times out? I will add it to the ticket.

We are only requesting for the first 1 issue which should not be an issue.
And you certainly don't have a unreasonable amount of issues.

@anuraghazra are you sure the syntax is correct maybe there was an API change.
No the (first: 1) syntax is valid, otherwise it would throw "invalid parameter" error.
And it certainly works for me and other users.

Seems like the issue is specifically with the pagination logic where requesting first: 1 fails the api request.

[rickstaa]

@anuraghazra Ah nice, I think we narrowed it down. I will add all the information to the ticket.

[Andre601]

Hope this will be resolved quick by GitHub. Would appreciate a comment here once they give their response to this...
(And just in case: I'm one of those people having issues)