-
Notifications
You must be signed in to change notification settings - Fork 48
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
Website no longer working due to "bad credentials" #70
Comments
@nianiaJR I got a couple of user complain about this lately, could you please help take a look at it when free? |
Looks like the issue has come back. |
what's the problem? I've tested it in my local env, it looks ok. |
index.js:286 Uncaught (in promise) Error: GraphQL Error (Code: 401): {"response":{"message":"Bad credentials","documentation_url":"https://docs.github.com/graphql","status":401},"request":{"query":"\n query searchRepository($query: String!){\n search(query: $query, first: 5, type: REPOSITORY) {\n codeCount\n nodes {\n ...on Repository {\n nameWithOwner\n }\n }\n }\n }\n ","variables":{"query":"Ap"}}} |
POST https://api.github.com/graphql 401 (Unauthorized) |
I think @nielifeng meant the serving version on github pages, that won't work now with the change removing hardcoded credentials. To enable that, we could further:
|
|
It's like that you don't have the access to the Github API, have you config your own token here https://github.com/vesoft-inc/github-statistics/blob/master/.env ? It has been described in the README |
Hi all, I fix this problem in pr #74 . please check and review my work. |
same problem |
Please check the FAQ documentation before raising an issue
Describe the bug (required)
The website is not working at all now. When a project is being typed in, nothing happens.
When you check the browser console, it gets filled with 401 errors from the GitHub GraphQL API with the response of "Bad credentials"
Your Environments (required)
How To Reproduce(required)
Steps to reproduce the behavior:
Expected behavior
Data is loaded, graphs are shown
Additional context
The text was updated successfully, but these errors were encountered: