Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Any plans to support newer Edge versions? #1

Open
dalgibbard opened this issue Mar 1, 2022 · 3 comments
Open

Question: Any plans to support newer Edge versions? #1

dalgibbard opened this issue Mar 1, 2022 · 3 comments
Assignees

Comments

@dalgibbard
Copy link

dalgibbard commented Mar 1, 2022

Firstly, Hi, and thanks for providing this :)

I was just curious if there's any scope to support a newer edge version, where this currently uses v.89 (and actually doesn't build locally for me, because the package doesn't seem to be in apt anymore)

I've tried various ways to build with v98, but so far no luck. I'm starting to assume that newer Edge versions/drivers just aren't Selenium3 compatible...
When trying with v98, I keep getting:

System info: host: '797e291277e1', ip: '172.17.0.2', os.name: 'Linux', os.arch: 'amd64', os.version: '5.10.60.1-microsoft-standard-WSL2', java.version: '1.8.0_212'
Driver info: driver.version: unknown
        at org.openqa.grid.internal.utils.configuration.json.CommonJsonConfiguration.fromJson(CommonJsonConfiguration.java:52)
        at org.openqa.grid.internal.utils.configuration.json.CommonJsonConfiguration.fromResourceOrFile(CommonJsonConfiguration.java:41)
        at org.openqa.grid.internal.utils.configuration.json.NodeJsonConfiguration.loadFromResourceOrFile(NodeJsonConfiguration.java:48)
        at java.util.Optional.map(Optional.java:215)
        at org.openqa.grid.internal.utils.configuration.GridNodeConfiguration.<init>(GridNodeConfiguration.java:203)
        at org.openqa.grid.selenium.GridLauncherV3.lambda$buildLaunchers$7(GridLauncherV3.java:275)
        at org.openqa.grid.selenium.GridLauncherV3.lambda$launch$0(GridLauncherV3.java:86)
        at java.util.Optional.map(Optional.java:215)
        at org.openqa.grid.selenium.GridLauncherV3.launch(GridLauncherV3.java:86)
        at org.openqa.grid.selenium.GridLauncherV3.main(GridLauncherV3.java:70)
Caused by: org.openqa.selenium.json.JsonException: Object coercer cannot determine proper type: END_MAP
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: '797e291277e1', ip: '172.17.0.2', os.name: 'Linux', os.arch: 'amd64', os.version: '5.10.60.1-microsoft-standard-WSL2', java.version: '1.8.0_212'
Driver info: driver.version: unknown

I get this even if I set JAVA_OPTS=-Dwebdriver.edge.driver=/opt/selenium/msedgedriver too.

Would appreciate your thoughts :)

@novak-dev
Copy link
Owner

I was able to get it to work with 95.0.1020.40 edge version. So I think it should be possible but need to find a way to automate the process of getting the latest version

@novak-dev
Copy link
Owner

Its fixed now, there was a bunch of json parsing errors, so the image is building successfully.

@novak-dev novak-dev self-assigned this Mar 2, 2022
@dalgibbard
Copy link
Author

dalgibbard commented Mar 2, 2022

Oh great! I noticed that the selenium team have a way of fetching the latest stable version in their gridv4 version here, which might help?: https://github.com/SeleniumHQ/docker-selenium/blob/trunk/NodeEdge/Dockerfile.txt

It would also be very handy to have a 'debug' version of the edge image (comes bundled with VNC for debugging and other integrations)?
Edit: that said, we can add that on our side if that's too niche of a requirement for here :) looks like they take the created node image, add vnc, and drop another supervisord config in:
https://github.com/SeleniumHQ/docker-selenium/blob/selenium-3/NodeChromeDebug/Dockerfile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants