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

time break too short #4

Open
ripoul opened this issue Apr 1, 2019 · 7 comments
Open

time break too short #4

ripoul opened this issue Apr 1, 2019 · 7 comments

Comments

@ripoul
Copy link
Contributor

ripoul commented Apr 1, 2019

I think this sleep is not enougth : I've got some strange random error while fetching the repositories of the organization.

By increasing the break time the error didn't show up again.

@ripoul ripoul changed the title sleep a little too short time break a little too short Apr 1, 2019
@ripoul ripoul changed the title time break a little too short time break too short Apr 1, 2019
@frinyvonnick
Copy link
Contributor

frinyvonnick commented Apr 1, 2019

Thanks for report 👍 How much did you increased it ?

@ripoul
Copy link
Contributor Author

ripoul commented Apr 1, 2019

*2 just to be sure...

@frinyvonnick
Copy link
Contributor

I don't have any problem but you could let the possibility to overwrite this time ? Maybe with cli option or env variable ?

@ripoul
Copy link
Contributor Author

ripoul commented Apr 1, 2019 via email

@ripoul
Copy link
Contributor Author

ripoul commented Apr 3, 2019

[GraphQL error]: Message: Something went wrong while executing your query. Please include `86B2:2609:350B9C:698E28:5CA4935E` when reporting this issue., Location: undefined, Path: undefined
{ Error: GraphQL error: Something went wrong while executing your query. Please include `86B2:2609:350B9C:698E28:5CA4935E` when reporting this issue.
    at new ApolloError (/home/ripoul/Documents/epsi/cloud/project/github-insight/node_modules/apollo-client/bundle.umd.js:59:32)
    at QueryManager.<anonymous> (/home/ripoul/Documents/epsi/cloud/project/github-insight/node_modules/apollo-client/bundle.umd.js:1183:49)
    at step (/home/ripoul/Documents/epsi/cloud/project/github-insight/node_modules/tslib/tslib.js:133:27)
    at Object.next (/home/ripoul/Documents/epsi/cloud/project/github-insight/node_modules/tslib/tslib.js:114:57)
    at /home/ripoul/Documents/epsi/cloud/project/github-insight/node_modules/tslib/tslib.js:107:75
    at new Promise (<anonymous>)
    at Object.__awaiter (/home/ripoul/Documents/epsi/cloud/project/github-insight/node_modules/tslib/tslib.js:103:16)
    at /home/ripoul/Documents/epsi/cloud/project/github-insight/node_modules/apollo-client/bundle.umd.js:1146:87
    at /home/ripoul/Documents/epsi/cloud/project/github-insight/node_modules/apollo-client/bundle.umd.js:1626:21
    at Array.forEach (<anonymous>)
  graphQLErrors:
   [ { message:
        'Something went wrong while executing your query. Please include `86B2:2609:350B9C:698E28:5CA4935E` when reporting this issue.' } ],
  networkError: null,
  message:
   'GraphQL error: Something went wrong while executing your query. Please include `86B2:2609:350B9C:698E28:5CA4935E` when reporting this issue.',
  extraInfo: undefined }
(node:5815) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'data' of undefined
    at /home/ripoul/Documents/epsi/cloud/project/github-insight/get.js:243:38
    at processTicksAndRejections (internal/process/next_tick.js:81:5)
(node:5815) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:5815) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Is that possible that appolo not hundle the rate limit ?

@frinyvonnick
Copy link
Contributor

There is a Cannot read property 'data' of undefined can you share the code of get.js in a gist ?

@ripoul
Copy link
Contributor Author

ripoul commented Apr 3, 2019

it's the next error created by the first one. You can find the code here.

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

No branches or pull requests

2 participants