[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)

[anuraghazra]

Found another thing.

Having both filters at once fails, but if i put one by one it works.
Fails :

    issues(states: [OPEN, CLOSED]) {
      totalCount
    }

Works

    issues(states: [CLOSED]) {
      totalCount
    }

Works

    issues(states: [OPEN]) {
      totalCount
    }

[rickstaa]

@Andre601 I will keep you updated. The ticket that I opened is https://support.github.com/ticket/personal/0/1369436. I however do think it is not public.

[Andre601]

#1406 (comment)

Can replicate this (Actually, I just wanted to write this when you commented).
My guess here is that GitHub just fails at retrieving both at once? Or maybe the total amount is important?

@Andre601 I will keep you updated. The ticket that I opened is https://support.github.com/ticket/personal/0/1369436. I however do think it is not public.

It already says in the URL "personal" so it should be obvious if the ticket is public...

[rickstaa]

@anuraghazra I added your info to the ticket.

@Andre601 I am aware, I however asked them to see if it is possible to make it public. I listed the ticket number here, might this be possible.

[rickstaa]

I however think that all tickets are private. I will keep you updated.

[sskorol]

Same issue. Stats are broken for me. I use the following layout:

<a target="_blank" href="https://github.com/sskorol">
  <img alt="Sergey's GitHub Stats" align="center" src="https://github-readme-stats.vercel.app/api/?username=sskorol&count_private=true&show_icons=true&theme=prussian&custom_title=GitHub%20Profile%20Summary&include_all_commits=true&hide_border=true&hide_rank=true" />
</a>

[rickstaa]

I got the following response from the GitHub Team:

It does appear you and the other users hit a timeout. The API(REST and GraphQL) has a timeout on processing requests and if that timeout is hit, the request is terminated and you get back an error. Currently, the timeout is 10 seconds. I have asked the engineering team to help take a further look at this particular timeout and check if it is indeed expected. I don't have an ETA now but will write back to you when I have any news.

[sskorol]

Was curious about timeout and changed the include_all_commits=true to false. And stats were successfully loaded in a preview mode.

[Andre601]

I got the following response from the GitHub Team:

It does appear you and the other users hit a timeout. The API(REST and GraphQL) has a timeout on processing requests and if that timeout is hit, the request is terminated and you get back an error. Currently, the timeout is 10 seconds. I have asked the engineering team to help take a further look at this particular timeout and check if it is indeed expected. I don't have an ETA now but will write back to you when I have any news.

Something I didn't ask, but what did you actually write in the ticket?

[rickstaa]

@Andre601 Of course no problem. As they state that tickets can not be made public I will past my initial question below. Besides that I added extra comments with all the information that was collected in #1406 #1405 and in this topic:

Dear Support Agent,

I just noticed that there is a bug in the graphql API. This bug is preventing the github-readme-stats tool from working (see https://github.com/anuraghazra/github-readme-stats/issues/1406). We narrowed the issue down to the following graphql syntax:

issues(first: 1) {
    totalCount
 }

The issue seems to be with the pagination logic. The strange thing is that it only happens for certain users (see a list of usernames in the issue above).

Thanks a lot in advance,
Greetings,
Rick

Reproduction Steps

    Go to the graphql explorer.
    Log in to your user account.
    Try to fetch the following grphql request:

{
  viewer {
    name
    login
    issues {
      totalCount
    }
  }
}

Fault Type

Permanent - Occurring repeatably

Blocking?

Blocking

Last working date

21 October

Logs

"\n\n \n <meta http-equiv="Content-type" content="text/html; charset=utf-8">\n <meta http-equiv="Content-Security-Policy" content="default-src 'none'; base-uri 'self'; connect-src 'self'; form-action 'self'; img-src data:; script-src 'self'; style-src 'unsafe-inline'">\n <meta content="origin" name="referrer">\n Oh snap! · GitHub\n <style type="text/css" media="screen">\n body {\n background-color: #f1f1f1;\n margin: 0;\n font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol";\n }\n\n .outer-container {\n position: relative;\n }\n\n .container {\n width: 600px;\n text-align: center;\n\n position: absolute;\n top: 50%;\n left: 50%;\n transform: translate(-50%, -50%);\n }\n\n a { color: #4183c4; text-decoration: none; }\n a:hover { text-decoration: underline; }\n\n h1 { letter-spacing: -1px; line-height: 60px; font-size: 60px; font-weight: 100; margin: 0px; text-shadow: 0 1px 0 #fff; }\n p { color: rgba(0, 0, 0, 0.5); margin: 20px 0 40px; }\n\n ul { list-style: none; margin: 25px 0; padding: 0; }\n li { display: table-cell; font-weight: bold; width: 1%; }\n\n .logo { display: inline-block; margin-top: 35px; }\n .logo-img-2x { display: none; }\n @media\n only screen and (-webkit-min-device-pixel-ratio: 2),\n only screen and ( min--moz-device-pixel-ratio: 2),\n only screen and ( -o-min-device-pixel-ratio: 2/1),\n only screen and ( min-device-pixel-ratio: 2),\n only screen and ( min-resolution: 192dpi),\n only screen and ( min-resolution: 2dppx) {\n .logo-img-1x { display: none; }\n .logo-img-2x { display: inline-block; }\n }\n\n #suggestions {\n margin-top: 35px;\n color: #ccc;\n }\n #suggestions a {\n color: #666666;\n font-weight: 200;\n font-size: 14px;\n margin: 0 10px;\n }\n\n .emoji {\n color: #000;\n line-height: 1;\n }\n\n \n \n \n\n <div class="container">\n\n Oh snap!\n \n Something, somewhere, has gone horribly, horribly wrong.\n If the problem persists, try refreshing your browser.\n \n <div id="suggestions">\n <a href="https://github.com/contact\">Contact Support —\n <a href="https://status.github.com\">GitHub Status —\n <a href="https://twitter.com/githubstatus\">@githubstatus\n \n\n <a href="/" class="logo logo-img-1x">\n <img width="32" height="32" title="" alt="" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAYAAABzenr0AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAyRpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADw/eHBhY2tldCBiZWdpbj0i77u/IiBpZD0iVzVNME1wQ2VoaUh6cmVTek5UY3prYzlkIj8+IDx4OnhtcG1ldGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IkFkb2JlIFhNUCBDb3JlIDUuMy1jMDExIDY2LjE0NTY2MSwgMjAxMi8wMi8wNi0xNDo1NjoyNyAgICAgICAgIj4gPHJkZjpSREYgeG1sbnM6cmRmPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgtbnMjIj4gPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIgeG1sbnM6eG1wPSJodHRwOi8vbnMuYWRvYmUuY29tL3hhcC8xLjAvIiB4bWxuczp4bXBNTT0iaHR0cDovL25zLmFkb2JlLmNvbS94YXAvMS4wL21tLyIgeG1sbnM6c3RSZWY9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC9zVHlwZS9SZXNvdXJjZVJlZiMiIHhtcDpDcmVhdG9yVG9vbD0iQWRvYmUgUGhvdG9zaG9wIENTNiAoTWFjaW50b3NoKSIgeG1wTU06SW5zdGFuY2VJRD0ieG1wLmlpZDpFMTZCRDY3REIzRjAxMUUyQUQzREIxQzRENUFFNUM5NiIgeG1wTU06RG9jdW1lbnRJRD0ieG1wLmRpZDpFMTZCRDY3RUIzRjAxMUUyQUQzREIxQzRENUFFNUM5NiI+IDx4bXBNTTpEZXJpdmVkRnJvbSBzdFJlZjppbnN0YW5jZUlEPSJ4bXAuaWlkOkUxNkJENjdCQjNGMDExRTJBRDNEQjFDNEQ1QUU1Qzk2IiBzdFJlZjpkb2N1bWVudElEPSJ4bXAuZGlkOkUxNkJENjdDQjNGMDExRTJBRDNEQjFDNEQ1QUU1Qzk2Ii8+IDwvcmRmOkRlc2NyaXB0aW9uPiA8L3JkZjpSREY+IDwveDp4bXBtZXRhPiA8P3hwYWNrZXQgZW5kPSJyIj8+SM9MCAAAA+5JREFUeNrEV11Ik1EY3s4+ddOp29Q5b0opCgKFsoKoi5Kg6CIhuwi6zLJLoYLopq4qsKKgi4i6CYIoU/q5iDAKs6syoS76IRWtyJ+p7cdt7sf1PGOD+e0c3dygAx/67ZzzPM95/877GYdHRg3ZjMXFxepQKNS6sLCwJxqNNuFpiMfjVs4ZjUa/pmmjeD6VlJS8NpvNT4QQ7mxwjSsJiEQim/1+/9lgMHgIr5ohuxG1WCw9Vqv1clFR0dCqBODElV6v90ogEDjGdYbVjXhpaendioqK07CIR7ZAqE49PT09BPL2PMgTByQGsYiZlQD4uMXtdr+JxWINhgINYhGT2MsKgMrm2dnZXgRXhaHAg5jEJodUAHxux4LudHJE9RdEdA+i3Juz7bGHe4mhE9FNrgwBCLirMFV9Okh5eflFh8PR5nK5nDabrR2BNJlKO0T35+Li4n4+/J+/JQCxhmu5h3uJoXNHPbmWZAHMshWB8l5/ipqammaAf0zPDDx1ONV3vurdidqwAQL+pEc8sLcAe1CCvQ3YHxIW8Pl85xSWNC1hADDIv0rIE/o4J0k3kww4xSlwIhcq3EFFOm7KN/hUGOQkt0CFa5WpNJlMvxBEz/IVQAxg/ZRZl9wiHA63yDYieM7DnLP5CiAGsC7I5sgtYKJGWe2A8seFqgFJrJjEPY1Cn3pJ8/9W1e5VWsFDTEmFrBcoDhZJEQkXuhICMyKpjhahqN21hRYATKfUOlDmkygrR4o4C0VOLGJKrOITKB4jijzdXygBKixyC5TDQdnk/Pz8qRw6oOWGlsTKGOQW6OH6FBWsyePxdOXLTgxiyebILZCjz+GLgMIKnXNzc49YMlcRdHXcSwxFVgTInQhC9G33UhNoJLuqq6t345p9y3eUy8OTk5PjAHuI9uo4b07FBaOhsu0A4Unc+T1TU1Nj3KsSSE5yJ65jqF2DDd8QqWYmAZrIM2VlZTdnZmb6AbpdV9V6ec9znf5Q7HjYumdRE0JOp3MjitO4SFa+cZz8Umqe3TCbSLvdfkR/kWDdNQl5InuTcysOcpFT35ZrbBxx4p3JAHlZVVW1D/634VRt+FvLBgK/v5LV9WS+10xMTEwtRw7XvqOL+e2Q8V3AYIOIAXQ26/heWVnZCVfcyKHg2CBgTpmPmjYM8l24GyaUHyaIh7XwfR9ErE8qHoDfn2LTNAVC0HX6MFcBIP8Bi+6F6cdW/DICkANRfx99fEYFQ7Nph5i/uQiA214gno7K+guhaiKg9gC62+M8eR7XsBsYJ4ilam60Fb7r7uAj8wFyuwM1oIOWgfmDy6RXEEQzJMPe23DXrVS7rtyD3Df8z/FPgAEAzWU5Ku59ZAUAAAAASUVORK5CYII=">\n \n\n <a href="/" class="logo logo-img-2x">\n <img width="32" height="32" title="" alt="" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAEAAAABACAYAAACqaXHeAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAyRpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADw/eHBhY2tldCBiZWdpbj0i77u/IiBpZD0iVzVNME1wQ2VoaUh6cmVTek5UY3prYzlkIj8+IDx4OnhtcG1ldGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IkFkb2JlIFhNUCBDb3JlIDUuMy1jMDExIDY2LjE0NTY2MSwgMjAxMi8wMi8wNi0xNDo1NjoyNyAgICAgICAgIj4gPHJkZjpSREYgeG1sbnM6cmRmPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgtbnMjIj4gPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIgeG1sbnM6eG1wPSJodHRwOi8vbnMuYWRvYmUuY29tL3hhcC8xLjAvIiB4bWxuczp4bXBNTT0iaHR0cDovL25zLmFkb2JlLmNvbS94YXAvMS4wL21tLyIgeG1sbnM6c3RSZWY9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC9zVHlwZS9SZXNvdXJjZVJlZiMiIHhtcDpDcmVhdG9yVG9vbD0iQWRvYmUgUGhvdG9zaG9wIENTNiAoTWFjaW50b3NoKSIgeG1wTU06SW5zdGFuY2VJRD0ieG1wLmlpZDpEQUM1QkUxRUI0MUMxMUUyQUQzREIxQzRENUFFNUM5NiIgeG1wTU06RG9jdW1lbnRJRD0ieG1wLmRpZDpEQUM1QkUxRkI0MUMxMUUyQUQzREIxQzRENUFFNUM5NiI+IDx4bXBNTTpEZXJpdmVkRnJvbSBzdFJlZjppbnN0YW5jZUlEPSJ4bXAuaWlkOkUxNkJENjdGQjNGMDExRTJBRDNEQjFDNEQ1QUU1Qzk2IiBzdFJlZjpkb2N1bWVudElEPSJ4bXAuZGlkOkUxNkJENjgwQjNGMDExRTJBRDNEQjFDNEQ1QUU1Qzk2Ii8+IDwvcmRmOkRlc2NyaXB0aW9uPiA8L3JkZjpSREY+IDwveDp4bXBtZXRhPiA8P3hwYWNrZXQgZW5kPSJyIj8+hfPRaQAAB6lJREFUeNrsW2mME2UYbodtt+2222u35QheoCCYGBQligIJgkZJNPzgigoaTEj8AdFEMfADfyABkgWiiWcieK4S+QOiHAYUj2hMNKgYlEujpNttu9vttbvdw+chU1K6M535pt3ubHCSyezR+b73eb73+t7vrfXsufOW4bz6+vom9/b23ovnNNw34b5xYGAgODg46Mbt4mesVmsWd1qSpHhdXd2fuP/Afcput5/A88xwymcdBgLqenp6FuRyuWV4zu/v759QyWBjxoz5t76+/gun09mK5xFyakoCAPSaTCazNpvNPoYVbh6O1YKGRF0u13sNDQ27QMzfpiAAKj0lnU6/gBVfAZW2WWpwwVzy0IgP3G73FpjI6REhAGA9qVRqA1b9mVoBVyIC2tDi8Xg24+dUzQiAbS/s7Ox8G2o/3mKCC+Zw0efzPQEfcVjYrARX3dbV1bUtHo8fMgt42f+Mp0yUTVQbdWsAHVsikdiHkHaPxcQXQufXgUBgMRxme9U0AAxfH4vFvjM7eF6UkbJS5qoQwEQGA57Ac5JllFyUVZZ5ckUEgMVxsK2jlSYzI+QXJsiyjzNEAJyJAzb/KQa41jJKL8pODMQiTEAymXw5n8/P0IjD3bh7Rgog59aanxiIRTVvV/oj0tnHca/WMrVwODwB3raTGxzkBg/gnZVapFV62Wy2n5AO70HM/5wbJ0QnXyQSaVPDIuNZzY0V3ntHMwxiwHA0Gj2Np7ecIBDgaDAYXKCQJM1DhrgJ3nhulcPbl8j4NmHe46X/g60fwbz3aewjkqFQaAqebWU1AOqyQwt8Id6qEHMc97zu7u7FGGsn7HAiVuosVw7P35C1nccdgSCxop1dHeZswmfHMnxBo6ZTk+jN8dl/vF7vWofDsa+MLN9oEUBMxOb3+1eoEsBVw6Zmua49r8YmhAKDiEPcMwBsxMiqQ+ixzPFxZyqRpXARG/YOr1ObFJ0gUskXBbamcR1OKmMUvDxHRAu8/LmY3jFLMUpFqz9HxG65smYJdyKyECOxDiEAe/p1gjF2oonivZAsxVgl2daa4EQWCW6J55qFAFFZiJWYLxNQy2qOSUzGRsyXCUDIeliwAHEO4WSlWQBRFoZakXcKmCXmyXAKs0Ve9vl8q42WoIYpJU4hV3hKcNs8m9gl7p/xQ73eF5kB4j5mNrWmTJRNwAzqiV1CxjVTZCIkEq+Z1bZFZSN2CenmVAFVy4Plz8xKAGWjjAKFk6lCBMDR/MJjLLMSQNm43xAiQKTaA+9/wewhDjL+JVI1kkTSSOTcKbMTwPqESAot6dn6Fr1gHwVJju6IRuyiByPuUUBAg5DGkAgBmxlvdgIEK9gDkohdY/BJo4CAG0R8miRSsGABkgVQs4KXu098IgUXSSRsFAoKZiVAVDY2WUiiPTjYRi41KwGisrGsLtlsth8Fiwnz2fBkQvWfRtlE3iF2yW63/yCacXZ1dW02GwGyTFaRd4idJnCKHRaCxYRHoG5LTKT6SyiToP1fJHbmAYPYRR0UnZQtMnA6s0zg+GZBlt0Gdo7EPHgpE3Q6nZ8YyLhc8Xj8MJh/aKTAY+5FPAKHLE7RdwuYJZmNwzyCMkBCYyKROJBMJl9B/PXXCjjmCmDOVzH3fiPpObEWGqoKe4EBl8v1hlqsdLvd23mkxHM9pc9kMpmno9HoeTii7ewbHEZPPx1ztLS1tV3AnGuMjiNjvbQFuHw6zDo5By7dTPAQNBgMLrRarTkSls1mnwT7uwp9virx9QzbW/HuV/j5d/b+6jniKlllP8lkeONJDk+dq9GsQTnC4fB1heO0K47Hwe7WdDr9nAKgXwOBwHI+C45Htj1d6sd429TUNEcmUdc+PRaLHcvn87dXW4ugzdsaGxufL94NFv9zi1J7GVbhlvb2dnaJ3SVrxfc+n2+NTsZ7/H7/Mr3g5XdSIHyJSH1PZ+7fToyl2+ErqilgZ4NaLYB9goVGaHjR93Hv1ZrU4XDsFT20kH3PObzbWk0CgG1jacVIUnAQb9F+VexyLMzkpcLv0IJV7AHQIOCAUYHx7v5qgScmYHtTqSAyZLEJTK22Bie4iq3xsqpm4SAf9Hq9a2DnJ4uLK3SEULcdRvp3i3zHySqpficxEdsQc1NrlYXXvR+O7qASSezXB+h1SuUomgg9LL8BUoV4749EIolKh+EiqWmqVEZlDgHks2pxHw7xTqUQw9J5NcAXOK10AGIoZ6Zli6JY6Z1Q461KoZ4NiKLHarW+KDsxlDUPHZ5zPQZqUVDPJsTqb5n9malbpAh8C2XXDLl62+WZIDFRUlNVOiwencnNU3aQEkL+cDMSoLvZo2fQB7AJssNAuFuvorlDVVkkg2I87+jo2K2QAVphDrfyViK5VqtO34OkaxXCp+7drdDBCAdubm6eidX+2WwqT5komwh4YQLk+H4aE93h8Xg2gvHekQZOGSgLZTLyDTLJ4Lx9/KZWKBSainT4Iy3FqQBfnUZR42PKQFksBr9QKVXCPusD3OiA/RkQ5kP8qV/Jl1WywAp/6+dcmPM2zL1UrUahe4JqfnWWKXIul3uUbfP8njAFLW1OFr3gdFtZ72cNH+PtQT7/brW+NXqJAHh0y9V8/U/A1U7AfwIMAD7mS3pCbuWJAAAAAElFTkSuQmCC">\n \n \n \n\n"

[rickstaa]

@Andre601 Let me know if you want me to add something.

[rickstaa]

@anuraghazra I verified that your hotfix works when dropping 81b6593.

[rickstaa]

@anuraghazra I just received the following reply from the GitHub Support:

Hi Rick,
It appears the author of the library shipped a fix and the issue is now resolved.

#1406 (comment)

I'll go ahead and mark this ticket as solved but do reach out again if you have any further concerns.

Regards,
GitHub Support

Are you satisfied with using the current hotfix or do you want me to state why the timeout issue should be fixed at their side?

[anuraghazra]

@anuraghazra I just received the following reply from the GitHub Support:

Hi Rick,
It appears the author of the library shipped a fix and the issue is now resolved.
#1406 (comment)
I'll go ahead and mark this ticket as solved but do reach out again if you have any further concerns.
Regards,
GitHub Support

WTF! How does my hotfix justifies the problem as "solved"?

Of course it should be fixed from their side, it's an literal issue with their API responses. There could be other services which might use their graphql apis and those will also suffer the same problem.

Give them this example error,

{
  "errors": [
    {
      "message": "Something went wrong while executing your query. Please include `E6A8:098D:10A0805:332E750:6176B687` when reporting this issue."
    }
  ]

[anuraghazra]

@rickstaa maybe you can tell them that this is certainly a major issue with the GitHub GraphQL API and should be communicated to the respective engineering teams.

[rickstaa]

@anuraghazra I was also surprised by the response. Such a response is however sadly not uncomment on tickets like this since companies are often highly protective of the time of their developers. I will try to reiterate the importance of solving this issue. I will send it to your gmail so you can review it before I send it. I can also post it here but I wanted to keep this issue clean.

[rickstaa]

Here is a quick update I and @anuraghazra again reiterated to GitHub that this issue must be solved. We received the following response:

Hi Rick,

Thanks for writing back to us!

I agree with you that the error is from GitHub side and as I earlier mentioned, the reason for the error is because the API request timeouts.

While GraphQL allows you to request as much data as you want, there is a limit on the processing time of that request on our end. If it takes more than 10 seconds to process the request and collect all the data you requested -- the request will be terminated and you'll get back an error.

Our recommendation is that you split the query into multiple requests until you stop hitting timeouts --I noticed this is what the author did in the hotfix.

I am happy to pass your feedback again to the engineering team but given the team's current backlog, I don't have an ETA for a response given the team's current backlog. I'll reach out to you again if I have any news or update.

Regards,

GitHub Support

For now, we, therefore, have to keep using the hotfix till GitHub fixes the issue. The downside of this is that the HotFix requests more data since it requests the same field twice. The agent has been notified about this. I will let you know when the ticket status changes.

[rickstaa]

One last update. It looks like the GH agent has just archived my ticket, which means that I'm no longer in the loop of whether they fixed this problem. I guess we have to keep using the workaround for now.

[Bharathkumarraju]

Hi everyone, I've added a hotfix for the issue for the moment, it should solve the issue for now. #1409

so what should i do to fix this ... i am getting the same error?

[rickstaa]

@Bharathkumarraju, I think the current issue you are experiencing is caused by #1471. As explained in #1471 (comment), the best way to solve this is to deploy your Vercel instance. You can find a guide on how this is done here.

[hugorsgarcia]

Well, I have to same problem. Don't work for my username but works fine for any other I tried

[rickstaa]

Well, I have to same problem. Don't work for my username but works fine for any other I tried

Hey @hugogacia360, Thanks for your question. I checked your account, and your cards seem to work when I use the following syntax:

[![Anurag's GitHub stats](https://github-readme-stats.vercel.app/api?username=hugogacia360)](https://github.com/anuraghazra/github-readme-stats)

[![Top Langs](https://github-readme-stats.vercel.app/api/top-langs/?username=hugogacia360)](https://github.com/anuraghazra/github-readme-stats)

Maybe you made a small typo 🤔.

[ayeshag7]

Hi, I've also been experiencing this same issue. But for me, it is not just my GitHub Stats Card that is broken. I can't see anyone else's GitHub Stats Card, either.

Also, my Top Language Stats Card is not working. It seems like all the links from my profile to Vercel Api are broken.

I must add that this problem started after I opened a new issue on a repository,

I can't see anyone's stats cards or top languages or anything else that's fetching information from GitHub.

Any suggestion to help me fix this would be appreciated. I'm quite lost. Should I contact GitHub support?

[rickstaa]

@ayeshag7 Is your issue fixed? I made some mistakes in the last commit (see #2048). It should be fixed now.

[ayeshag7]

@ayeshag7 Is your issue fixed? I made some mistakes in the last commit (see #2048). It should be fixed now.

Yes, my problem is fixed now. Thanks.

[Rudxain]

(replying to main comment)
Related: https://github-readme-stats.vercel.app/api/top-langs/?username=Mojang shows this

Could not resolve to a User with the login of 'Mojang'.

[rickstaa]

(replying to main comment) Related: https://github-readme-stats.vercel.app/api/top-langs/?username=Mojang shows this

Could not resolve to a User with the login of 'Mojang'.

The error you are getting is that you are trying to request stats for an organization. Which is currently not supported. A feature request for this feature can be found on #654. You can show your support there.

[Rudxain]

you are trying to request stats for an organization. [ ... ] A feature request for this feature can be found on #654.

Thanks for the info! I'll go there