You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to run webdriver-manager update results in following error
[01:39:17] I/config_source - curl -o/usr/lib/node_modules/protractor/node_modules/webdriver-manager/selenium/standalone-response.xml https://selenium-release.storage.googleapis.com/
[01:39:18] E/downloader - options.uri is a required argument
[01:39:18] I/update - chromedriver: file exists /usr/lib/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_100.0.4896.60.zip
[01:39:18] I/update - chromedriver: unzipping chromedriver_100.0.4896.60.zip
/usr/lib/node_modules/protractor/node_modules/webdriver-manager/built/lib/cmds/update.js:232
throw new Error(`Invalid filename: ${path.resolve(outputDir, fileName)}`);
^
Error: Invalid filename: /usr/lib/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_100.0.4896.60.zip
at unzip (/usr/lib/node_modules/protractor/node_modules/webdriver-manager/built/lib/cmds/update.js:232:19)
at /usr/lib/node_modules/protractor/node_modules/webdriver-manager/built/lib/cmds/update.js:205:13
Probably due to the output of os.type() being Linux, but os.arch() being arm64 by default, but the wording of the error doesn't help very much in reaching that conclusion.
(I thought running docker with --platform=linux/amd64 would fix this, it moves past this error, but it leads to an error spawning chromium)
The text was updated successfully, but these errors were encountered:
Trying to run webdriver-manager update results in following error
Probably due to the output of os.type() being Linux, but os.arch() being arm64 by default, but the wording of the error doesn't help very much in reaching that conclusion.
(I thought running docker with --platform=linux/amd64 would fix this, it moves past this error, but it leads to an error spawning chromium)
The text was updated successfully, but these errors were encountered: