webdriver-manager: Error: Failed to make Github request, rate limit reached.

I am running webdriver-manager start and I get the following error and webdriver fails to start

(node:58736) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Failed to make Github request, rate limit reached. (node:58736) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js proces

Anyone else is seeing this issue?

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 14
  • Comments: 23 (3 by maintainers)

Commits related to this issue

Most upvoted comments

It will not help if you like to run the tests in firefox… 😒

This feature was resolved and released in the beta release of this and Protractor.

Still having the issue with gecko driver for firefox. The problem is this file is downloaded from api.github.com so i if you make too many requests at a given moment it fails. It’s not a reliable solution 😦

Solution suggested by @p3x-robot in the link helped me as well.

Same error: It is still the same error: https://travis-ci.org/patrikx3/angular-compile

Running "cory-ensure-protractor" task
Protractor found on the path[15:35:31] I/update - chromedriver: file exists /home/travis/build/patrikx3/angular-compile/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.37.zip
[15:35:31] I/update - chromedriver: unzipping chromedriver_2.37.zip
[15:35:32] I/update - chromedriver: setting permissions to 0755 for /home/travis/build/patrikx3/angular-compile/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.37
[15:35:32] I/update - chromedriver: chromedriver_2.37 up to date
[15:35:32] I/update - selenium standalone: file exists /home/travis/build/patrikx3/angular-compile/node_modules/protractor/node_modules/webdriver-manager/selenium/selenium-server-standalone-3.11.0.jar
[15:35:32] I/update - selenium standalone: selenium-server-standalone-3.11.0.jar up to date
(node:7143) UnhandledPromiseRejectionWarning: Error: Failed to make Github request, rate limit reached.
    at Request.req.on.response (/home/travis/build/patrikx3/angular-compile/node_modules/protractor/node_modules/webdriver-manager/built/lib/binaries/config_source.js:155:28)
    at Request.emit (events.js:180:13)
    at Request.onRequestResponse (/home/travis/build/patrikx3/angular-compile/node_modules/request/request.js:1068:10)
    at ClientRequest.emit (events.js:180:13)
    at HTTPParser.parserOnIncomingClient (_http_client.js:540:21)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:117:17)
    at TLSSocket.socketOnData (_http_client.js:445:20)
    at TLSSocket.emit (events.js:180:13)
    at addChunk (_stream_readable.js:274:12)
    at readableAddChunk (_stream_readable.js:261:11)
(node:7143) 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:7143) [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.

In my case, I think I made the mistake by installing both protractor and webdriver-manager globally. I uninstalled both the global packages and then installed just protractor. This resolved the “Rate limit” issue for me!

@mihaivarga do you know what to expect in Protractor 6? I still have no clue what the supposed fix is about.

Right now the github api limit only gets hit by us rather rare.

We have different needs, in my case this is used in a CI test framework running on servers on a daily basis. Something failing occasionally even rarely is not fine for us. This fix is clearly a very hacky patch but at least it always works as long as you don’t need the updates.

@virgile-hogman haven’t spent much time to investigate, gecko-driver issues seems to be fixed. I dropped it as it is beta and our working tests on 5+ where failing on 6 beta. I don’t know if there are any plans on releasing a new 5+ with the latest webdriver-manager that might fix the issue.

When using protractor 6.0.0-beta (which has webdriver manager beta) webdriver-manager update works fine. However we run into a lot of other issues with the e2e tests. Not a good viable solution. We need a solution for protractor 5 first. 😢