[rust] Update PATH processing mechanism by Selenium Manager#12291
[rust] Update PATH processing mechanism by Selenium Manager#12291bonigarcia merged 2 commits intotrunkfrom
Conversation
Codecov ReportPatch and project coverage have no change.
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. Additional details and impacted files@@ Coverage Diff @@
## trunk #12291 +/- ##
=======================================
Coverage 56.92% 56.92%
=======================================
Files 86 86
Lines 5423 5423
Branches 193 193
=======================================
Hits 3087 3087
Misses 2143 2143
Partials 193 193 ☔ View full report in Codecov by Sentry. |
diemol
left a comment
There was a problem hiding this comment.
WARN Incompatible release of chromedriver (version 107.0.5304.62) detected in PATH: C:\Users\boni\Documents\bat\chromedriver.exe
I believe ChromeDriver 114 works with Chrome 115 (and 116?), right? Should we change this message to something like:
WARN Release of chromedriver (version 107.0.5304.62) detected in PATH: C:\Users\boni\Documents\bat\chromedriver.exe does not match chrome 114.0.5735.199, session might be unstable or not start
Maybe avoiding the "incompatible" and noting the consequence of the incompatibility is more helpful for users.
Aside of that, it looks good to me, thanks @bonigarcia!
|
I like mentioning both versions. I think "incompatible" is fine; they are almost always going to see this warning just before a big error message about the versions being mismatched. Maybe we should explicitly suggest the recommended solution in the warning?
|
|
Indeed, "incompatible" is not always accurate since drivers are typically compatible with several browser versions. So yes, both of your messages are better since they provide more info. I have just added a new commit changing it. |
Description
This PR modifies the behaviour of Selenium Manager with respect to the way in which the drivers in PATH are processed.
Motivation and Context
This PR fixes #12177. The output to the proposed scenarios is as follows:
Old driver on PATH with Internet
Current driver on PATH with Internet
Old driver on PATH without Internet
Current driver on PATH without Internet
Current driver on PATH with Internet but invalid proxy
Types of changes
Checklist