Fix Session failing run using the chromerdriver binary #148
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses an issue where session execution is failing due to compatibility problems with the current ChromeDriverManager. At the moment, running the session has become increasingly complex and prone to errors.
To mitigate this issue temporarily, this fix introduces a direct approach: passing the ChromeDriver binary explicitly. This solution ensures stability and functionality until ChromeDriverManager is updated with the latest improvements and repositories.
Given the current limitations of the ChromeDriverManager, this approach provides a straightforward and effective workaround to unblock session execution while waiting for upstream fixes.
Changes
Next Steps