carocad commented on issue #7435: URL: https://github.com/apache/incubator-devlake/issues/7435#issuecomment-2122171826
> ... I can also contact the administrators on our side and ask if they can set one but since this is the default behavior from Github Server I would assume that this wouldn't be an isolated case. I just got an answer from the administrators on my site. The GraphQL endpoints on our side already have a rate limit so this shouldn't be the case. I also tried querying it myself and got an response without any issues. I submitted from the github.com docs (see [ref](https://docs.github.com/en/graphql/overview/rate-limits-and-node-limits-for-the-graphql-api#checking-the-status-of-your-primary-rate-limit)) ```graphql query { viewer { login } rateLimit { limit remaining used resetAt } } ``` I don't know which query does dev-lake uses but I can only guess that one of the fetched parameters was introduced on a version of github newer than `3.11.9`. In any case, my proposal above still stands. If you point me in the right direction I can definitely give it a try :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
