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
{{ message }}
This repository has been archived by the owner on Apr 1, 2019. It is now read-only.
I was working with a colleague to update their chromedriver and noticed that chromedriver-update, when invoked without a version argument, no-ops if a version of chromedriver is already downloaded. This seems unintuitive. I'd expect invoking chromedriver-update to fetch the latest version of chromedriver regardless of the currently-installed version. Is this intentional behavior? If so, even outputting a message informing the user that no update will be performed unless they remove the current version would be helpful. Or supporting an override flag to force the upgrade. Or anything except for exiting silently with no action. :)
The text was updated successfully, but these errors were encountered:
I was working with a colleague to update their chromedriver and noticed that
chromedriver-update
, when invoked without a version argument, no-ops if a version of chromedriver is already downloaded. This seems unintuitive. I'd expect invokingchromedriver-update
to fetch the latest version of chromedriver regardless of the currently-installed version. Is this intentional behavior? If so, even outputting a message informing the user that no update will be performed unless they remove the current version would be helpful. Or supporting an override flag to force the upgrade. Or anything except for exiting silently with no action. :)The text was updated successfully, but these errors were encountered: