Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[INFO] Common Error Codes (PLEASE CHECK FIRST) #1772

Open
rickstaa opened this issue May 18, 2022 · 38 comments
Open

[INFO] Common Error Codes (PLEASE CHECK FIRST) #1772

rickstaa opened this issue May 18, 2022 · 38 comments
Labels
important Important repo information.

Comments

@rickstaa
Copy link
Collaborator

rickstaa commented May 18, 2022

Here you can find common error codes. Please check this list and the existing issues before creating a new issue. For commonly asked questions, see the FAQ.

General errors

Maximum retries exceeded

image

This is likely caused by the public Vercel instance reaching one of the Github GraphQL limits. Multiple PAT tokens have been used to overcome these limits (see github-readme-stats/blob/master/src/common/retryer.js) but due to the popularity of GitHub-readme-stats, they sometimes run out. The best solution is to deploy your own Vercel instance. Please check this guide on how this is done. You can find more information on this problem in #1471. You can also use #1471 to check if the Public Vercel instance is down and to let us know the limits are continuously being reached.

⚠️ PLEASE READ ⚠️

Only comment on #1471 if nobody has commented in the last three days or if you have information that could help us solve the problem. If there already is a recent comment or the label is attached, we are aware of the issue and are working on it. 🤓 Comments like "+1" and "same here" don't help anyone; they pressure the maintainer and spam their inbox. 💥

@rickstaa rickstaa changed the title Common error codes (PLEASE READ FIRST) COMMON ERROR CODES (PLEASE READ) May 18, 2022
@rickstaa rickstaa changed the title COMMON ERROR CODES (PLEASE READ) COMMON ERROR CODES May 18, 2022
@rickstaa rickstaa pinned this issue May 18, 2022
@rickstaa rickstaa changed the title COMMON ERROR CODES Common Errors May 18, 2022
@rickstaa rickstaa changed the title Common Errors Common Error Codes (Please check first) May 18, 2022
@rickstaa rickstaa changed the title Common Error Codes (Please check first) Common Error Codes (PLEASE CHECK FIRST) May 18, 2022
@rickstaa
Copy link
Collaborator Author

Please comment below if you think an error code is missing from this list 👍🏻.

@rickstaa rickstaa added the important Important repo information. label May 19, 2022
@rickstaa rickstaa changed the title Common Error Codes (PLEASE CHECK FIRST) [INFO] Common Error Codes (PLEASE CHECK FIRST) May 19, 2022
@xorinzor

This comment was marked as off-topic.

@rickstaa
Copy link
Collaborator Author

rickstaa commented May 20, 2022

You can also use this issue to let us know the limits are being reached.

I just spotted this error.

@xorinzor Thanks for letting us know. I, however, meant #1471. Somebody already flagged the problem there, so I added the label to show that we are aware of the issue. I updated the text in this issue to:

You can also use #1471 to let us know the limits are being reached.

For now, I would advise people to deploy their own Vercel instance to lower the server load. Please check this guide on how this is done

@cristian-rincon

This comment was marked as off-topic.

@rickstaa
Copy link
Collaborator Author

rickstaa commented May 21, 2022

@cristian-rincon Please limit the discussion of the Maximum retries exceeded error to #1471.

@rickstaa
Copy link
Collaborator Author

@duaneking, thanks for your message. The hide parameter is working fine for me:

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

Top Langs

Can you maybe share the syntax you are using and a screenshot of the error message you receive?

@duaneking
Copy link

duaneking commented May 24, 2022

Any attempt to use the hide param multiple times results in this error:

image

In this case for the use of:

https://github-readme-stats.vercel.app/api/top-langs/?username=duaneking&hide=XML,CSS&theme=tokyonight&layout=compact&hide=rich%20text%20format&langs_count=8

I see that this is fixable by simply using it only once, but the expectation I had was that options would be merged. You may want to update the docs or fix the issue to provide better compatibility.

@rickstaa
Copy link
Collaborator Author

rickstaa commented May 24, 2022

I understand that the error is a bit vague. 😐It is a javascript error that we do catch. In your case, it is thrown since you use the hide property multiple times. In your case the proper syntax is:

[![Top Langs](https://github-readme-stats.vercel.app/api/top-langs/?username=duaneking&hide=XML,Rich%20Text%20Format&theme=tokyonight&layout=compact&langs_count=8)](https://github.com/anuraghazra/github-readme-stats)

Top Langs

@duaneking
Copy link

Yes but the expectation I have as a web developer is that multiple args will be merged.

Its a small thing, but should be documented or fixed. Thanks.

@rickstaa
Copy link
Collaborator Author

Yes but the expectation I have as a web developer is that multiple args will be merged.

Its a small thing, but should be documented or fixed. Thanks.

I agree. Feel free to open a pull request or a feature request issue! 🚀

@rickstaa
Copy link
Collaborator Author

I would prefer implementing the merging of multiple arguments than document that we do not merge arguments. 🙂

@fzyzcjy
Copy link

fzyzcjy commented May 28, 2022

@rickstaa
Copy link
Collaborator Author

rickstaa commented May 29, 2022

@fzyzcjy I'm not sure why you received that error. You're using the correct syntax, and it seems to work on my end. Maybe something else went wrong on the Vercel server, and we are not catching the correct error. Feel free to comment again if the issue persists.

Anurag's GitHub stats

[![Anurag's GitHub stats](https://github-readme-stats.vercel.app/api?username=anuraghazra&show_icons=true&count_private=true&locale=en)](https://github.com/anuraghazra/github-readme-stats)

Fzyzcjy's GitHub stats

[![Fzyzcjy's GitHub stats](https://github-readme-stats.vercel.app/api?username=fzyzcjy&show_icons=true&count_private=true&locale=en)](https://github.com/anuraghazra/github-readme-stats)

Fzyzcjy's GitHub stats

[![Fzyzcjy's GitHub stats](https://github-readme-stats.vercel.app/api?username=fzyzcjy&show_icons=true&locale=en&count_private=true)](https://github.com/anuraghazra/github-readme-stats)

@fzyzcjy
Copy link

fzyzcjy commented May 29, 2022

@rickstaa Hi thanks for the reply! It happens once in a while - e.g. it is fine now, but many times it just fails.

@rickstaa
Copy link
Collaborator Author

@fzyzcjy I also sometimes noticed this behaviour on my card. Maybe because of the significant number of commits on your account the card rendering reached a timeout. Perhaps we need to optimize the code a bit. Feel free to open an issue if the problem shows up more frequently.

@fzyzcjy
Copy link

fzyzcjy commented May 29, 2022

@rickstaa Thanks for the reply :)

@abhi1693
Copy link

abhi1693 commented Jul 6, 2022

Cannot read property 'data' of undefined

image

https://github-readme-stats.vercel.app/api?username=abhi1693&count_private=true

Not working for me

@EleoXDA
Copy link

EleoXDA commented Jul 12, 2022

Hi. Wanted to forward my question here. In short, the question is "how to hide C++ language from card"? The long version here:
#1516 (comment)

@rickstaa
Copy link
Collaborator Author

rickstaa commented Jul 13, 2022

@abhi1693 I checked your account and it looks like an error is thrown while trying to fetch your data using the GraphQL API. I suspect this is due to a timeout or limit set by the GitHub team (see #1406). You can see this using the following syntax in the GitHub GraphQL explorer:

query userInfo($login: String!) {
  user(login: $login) {
    name
    login
    contributionsCollection {
      totalCommitContributions
      restrictedContributionsCount
    }
    repositoriesContributedTo(
      first: 1
      contributionTypes: [COMMIT, ISSUE, PULL_REQUEST, REPOSITORY]
    ) {
      totalCount
    }
    pullRequests(first: 1) {
      totalCount
    }
    openIssues: issues(states: OPEN) {
      totalCount
    }
    closedIssues: issues(states: CLOSED) {
      totalCount
    }
    followers {
      totalCount
    }
    repositories(
      first: 100
      ownerAffiliations: OWNER
      orderBy: {direction: DESC, field: STARGAZERS}
    ) {
      totalCount
      nodes {
        stargazers {
          totalCount
        }
      }
    }
  }
}
{"login": "abhi1693"}

I think it is best to add your problem to #1406 and contact the GitHub team to check what is going wrong while fetching data for your account.

@dangolbeeker
Copy link

The following syntax seems to work. The &tsdsfs=sdfdsf is there to break the cache.

![Anurag's GitHub stats](https://github-readme-stats.vercel.app/api?username=dangolbeeker&tsdsfs=sdfdsf&hide=contribs,prs)

Anurag's GitHub stats

It came back to life on it's own.

@abhi1693
Copy link

abhi1693 commented Oct 5, 2022

@abhi1693 I checked your account and it looks like an error is thrown while trying to fetch your data using the GraphQL API. I suspect this is due to a timeout or limit set by the GitHub team (see #1406). You can see this using the following syntax in the GitHub GraphQL explorer:

query userInfo($login: String!) {
  user(login: $login) {
    name
    login
    contributionsCollection {
      totalCommitContributions
      restrictedContributionsCount
    }
    repositoriesContributedTo(
      first: 1
      contributionTypes: [COMMIT, ISSUE, PULL_REQUEST, REPOSITORY]
    ) {
      totalCount
    }
    pullRequests(first: 1) {
      totalCount
    }
    openIssues: issues(states: OPEN) {
      totalCount
    }
    closedIssues: issues(states: CLOSED) {
      totalCount
    }
    followers {
      totalCount
    }
    repositories(
      first: 100
      ownerAffiliations: OWNER
      orderBy: {direction: DESC, field: STARGAZERS}
    ) {
      totalCount
      nodes {
        stargazers {
          totalCount
        }
      }
    }
  }
}
{"login": "abhi1693"}

I think it is best to add your problem to #1406 and contact the GitHub team to check what is going wrong while fetching data for your account.

@rickstaa I checked with GitHub team and it's not working for me because I have too much data to fetch in a single go. My amount of commits alone is beyond what normal user has. So, it's safe to assume that this app won't work for me until some sort of smart mechanism is applied for such edge cases.

@rickstaa
Copy link
Collaborator Author

rickstaa commented Oct 7, 2022

@abhi1693 I checked your account and it looks like an error is thrown while trying to fetch your data using the GraphQL API. I suspect this is due to a timeout or limit set by the GitHub team (see #1406). You can see this using the following syntax in the GitHub GraphQL explorer:

query userInfo($login: String!) {
  user(login: $login) {
    name
    login
    contributionsCollection {
      totalCommitContributions
      restrictedContributionsCount
    }
    repositoriesContributedTo(
      first: 1
      contributionTypes: [COMMIT, ISSUE, PULL_REQUEST, REPOSITORY]
    ) {
      totalCount
    }
    pullRequests(first: 1) {
      totalCount
    }
    openIssues: issues(states: OPEN) {
      totalCount
    }
    closedIssues: issues(states: CLOSED) {
      totalCount
    }
    followers {
      totalCount
    }
    repositories(
      first: 100
      ownerAffiliations: OWNER
      orderBy: {direction: DESC, field: STARGAZERS}
    ) {
      totalCount
      nodes {
        stargazers {
          totalCount
        }
      }
    }
  }
}
{"login": "abhi1693"}

I think it is best to add your problem to #1406 and contact the GitHub team to check what is going wrong while fetching data for your account.

@rickstaa I checked with GitHub team and it's not working for me because I have too much data to fetch in a single go. My amount of commits alone is beyond what normal user has. So, it's safe to assume that this app won't work for me until some sort of smart mechanism is applied for such edge cases.

The strange thing is that this timeout only occurs for me when using the GraphQL API through https://api.github.com/graphql as we do in GRS. When doing so, I will get the following error:

{
    status: 502,
    statusText: "Bad Gateway",
    message: 'Something went wrong while executing your query. This may be the result of a timeout, or it could be a GitHub bug.  
    Please include `A0B6:EC6F:57AF040:58F6D1E:63404A63` when reporting this issue.'
}

When I try to fetch your data using the GraphQL explorer:

query userInfo($login: String!) {
  user(login: $login) {
    name
    login
    contributionsCollection {
      totalCommitContributions
      restrictedContributionsCount
    }
    repositoriesContributedTo(
      contributionTypes: [COMMIT, ISSUE, PULL_REQUEST, REPOSITORY]
    ) {
      totalCount
    }
    pullRequests {
      totalCount
    }
    openIssues: issues(states: OPEN) {
      totalCount
    }
    closedIssues: issues(states: CLOSED) {
      totalCount
    }
    followers {
      totalCount
    }
    repositories(ownerAffiliations: OWNER) {
      totalCount
    }
  }
}
{
  "login": "abhi1693"
}

I will correctly receive your data:

{
  "data": {
    "user": {
      "name": "Abhimanyu Saharan",
      "login": "abhi1693",
      "contributionsCollection": {
        "totalCommitContributions": 295,
        "restrictedContributionsCount": 16498
      },
      "repositoriesContributedTo": {
        "totalCount": 83
      },
      "pullRequests": {
        "totalCount": 105
      },
      "openIssues": {
        "totalCount": 44
      },
      "closedIssues": {
        "totalCount": 155
      },
      "followers": {
        "totalCount": 15
      },
      "repositories": {
        "totalCount": 62
      }
    }
  }
}

Maybe you can give the support A0B6:EC6F:57AF040:58F6D1E:63404A63 so they can investigate this issue further.

@fzyzcjy
Copy link

fzyzcjy commented Nov 27, 2022

Hi, the card for me (link: https://github.com/fzyzcjy) seems not to work anymore. It always shows the following. As mentioned before, this may be caused by the number of commits. However, originally the card can be successfully loaded every several retries, but now it seems never to be successfully loaded. :(

image

@rickstaa
Copy link
Collaborator Author

rickstaa commented Dec 2, 2022

Hi, the card for me (link: https://github.com/fzyzcjy) seems not to work anymore. It always shows the following. As mentioned before, this may be caused by the number of commits. However, originally the card could be successfully loaded every several retries, but now it seems never to be successfully loaded. :(

image

@fzyzcjy Thanks for your bug report. Yea, I noticed that bug also on my README. I assume it happens for users for which we have to pull a lot of data from the GrapQL API. Although some users have even too much data for the GraphQL API request to complete (see #1406) for your account, the request on the server is successful. It simply takes too long for githubs CDN, resulting in a timeout when the card is not found in the cache. 😅 The card will then show up when you refresh the page again. This problem will be solved when #2179 is implemented, so it's best to subscribe to it.

@fzyzcjy
Copy link

fzyzcjy commented Dec 3, 2022

@rickstaa Hi thanks for the information!

Btw the card frequently does not show up even after a few refreshes, but sometimes it does appear after a few refreshes.

@rickstaa
Copy link
Collaborator Author

rickstaa commented Dec 3, 2022

@rickstaa Hi thanks for the information!

Btw the card frequently does not show up even after a few refreshes, but sometimes it does appear after a few refreshes.

Yea, I also noticed that behaviour. I think it is best to go with the new GitHub Action I'm planning to implement for your account. 🤔

@Dawid-Witkowski
Copy link

I'm not sure whether a large amount of data is the case, I'm also experiencing the same issue:
image
and I don't have that much data yet, should I just wait for the update? @rickstaa

@msaserj
Copy link

msaserj commented Dec 29, 2022

widget_readme_stats
Hello. It looks like the widgets are broken. 🤔

@Dawid-Witkowski
Copy link

@msaserj that's already solved, check: #2287 (comment)

@rickstaa
Copy link
Collaborator Author

@msaserj that's already solved, check: #2287 (comment)

@dawwit0001, thank you for helping us maintain this repository 🚀. I checked your previous question, and that does happen to me also from time to time. It occurs because the Vercel function reaches GitHub's CDN timeout. The card, however, is correctly cached on the server and will show the next time somebody visits. This problem will be solved when I implement #2179.

@Rikveet
Copy link

Rikveet commented Jan 6, 2023

Cannot read property 'user' of undefined

https://github-readme-stats.vercel.app/api?username=fzyzcjy&show_icons=true&locale=en&count_private=true

image

I had the same issue but when I just directly searched the address in the browser it worked.
Figured out that I was entering my username in an incorrect manner.
The first letter was capitalised which was causing the issue.

@Harkirattttt
Copy link

Hello can you please help me fix this error?
image

@jonesy-b-dev
Copy link

Getting this error, didnt see it anywhere here yet. Way to fix it?
image

@qwerty541
Copy link
Collaborator

Getting this error, didnt see it anywhere here yet. Way to fix it? image

Answered in #3429 (comment)

@Chhunneng
Copy link

I got error on github

Screenshot 2023-11-12 at 8 31 57

@qwerty541
Copy link
Collaborator

I got error on github

Screenshot 2023-11-12 at 8 31 57

Hey, @Chhunneng! The problem is with GitHub's CDN. The only way to solve this is to create a GitHub action. You can track progress on this feature at #2179.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
important Important repo information.
Projects
None yet
Development

No branches or pull requests