[🐛 Bug]: Unable to find an exact match for CDP version {0}...

[kool79]

What happened?

Placeholders are not replaced in the Warning message:
"Unable to find an exact match for CDP version {0}, returning the closest version; found: {1}; Please update to a Selenium version that supports CDP version {0} "

Screenshot below:

Selenium v.4.25.0, OpenJDK23,win 10

[github-actions]

@kool79, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[pujagani]

Thank you for reporting the issue. I am unable to reproduce it on my end, I think it is because I am using Java 17.0.12. Would you like to contribute to Selenium to help fix this? Thank you!

[github-actions]

This issue is looking for contributors.

Please comment below or reach out to us through our IRC/Slack/Matrix channels if you are interested.

[preetisaini1]

@kool79 Can you share the Browser and the Browser Version where the issue was seen. Also would be nice if you could share the browserDriver version if was explicitly provided when starting the browser session here

[kool79]

My webdriver is 4.25.0, Browser chrome 131.0.6778.70.
I think that browser version is not important here, because the bug is about log message formatting.

Maybe it is a logger issue, because during debugging I see all parameters are correct.

[Delta456]

If we want to support older Java versions. We need to shift to C style string formatting. What do you think @pujagani?

[pujagani]

The logging style we currently use is across our Java bindings and that is the preferred approach. It is working well for JDK17. I am sensing it could be the Java version. Were you able to reproduce this issue @Delta456 ?

[Delta456]

The logging style we currently use is across our Java bindings and that is the preferred approach. It is working well for JDK17. I am sensing it could be the Java version. Were you able to reproduce this issue @Delta456 ?

I wasn't able to reproduce this issue as well.

[pujagani]

@Delta456 Even with JDK23?

[Delta456]

Yes

[pujagani]

The code uses Java logging so it shouldn't be a logger issue.
@kool79 Can you please try to see if you run the code in the command line and face the same issue? Just trying to eliminate IDE-specific issues here. Thank you!