From Newsgroup: rec.sport.rowing

<div>When Firefox is packaged inside a container (like the default Firefox browser</div><div></div><div>shipped with Ubuntu 22.04), it may see a different filesystem to the host.</div><div></div><div>This can affect access to the generated profile directory, which may result</div><div></div><div>in a hang when starting Firefox. Workarounds are listed in the geckodriver</div><div></div><div>usage documentation.</div><div></div><div></div><div>After enabling the site-isolation feature in Firefox with geckodriver 0.32.1</div><div></div><div>some WebDriver clients like Selenium that use the Chrome DevTools Protocol (CDP)</div><div></div><div>by default for logging events could trigger a hang in Firefox's experimental CDP</div><div></div><div>implementation. The fix for this problem will be shipped with Firefox 112.</div><div></div><div>Until then the following Firefox preferences should be set:</div><div></div><div></div><div></div><div></div><div></div><div>download firefox geckodriver</div><div></div><div>Download File: https://t.co/Pn8no4pJ3Y </div><div></div><div></div><div>Using geckodriver to launch Firefox inside a sandbox -- for example a Firefox distribution using Snap or Flatpak -- can fail with a "Profile not found" error if the sandbox restricts Firefox's ability to access the system temporary directory. geckodriver uses the temporary directory to store Firefox profiles created during the run.</div><div></div><div></div><div>This issue can now be worked around by using the --profile-root command line option or setting the TMPDIR environment variable to a location that both Firefox and geckodriver have read/write access to e.g.:</div><div></div><div></div><div>Note: The actual validation can only be performed if the machine that starts the geckodriver binary for the very first time is online. You can find more details on how to work around this issue in the macOS notarization section of the documentation.</div><div></div><div></div><div>Using geckodriver to launch Firefox inside a sandbox -- for example</div><div></div><div>a Firefox distribution using Snap or Flatpak -- can fail with a</div><div></div><div>"Profile not found" error if the sandbox restricts Firefox's ability</div><div></div><div>to access the system temporary directory. geckodriver uses the</div><div></div><div>temporary directory to store Firefox profiles created during the run.</div><div></div><div></div><div>By default any request with an Origin header is rejected, and only requests</div><div></div><div>containing the bound hostname (specified via --host), or an IP address,</div><div></div><div>in the Host header are allowed. These configuration options are</div><div></div><div>designed to support scenarios where geckodriver is running on a different</div><div></div><div>network node to the host e.g. some container based setups.</div><div></div><div></div><div>geckodriver restricts connections to local IP addresses. This can interfere</div><div></div><div>with deployments in which geckodriver is running on a different network node</div><div></div><div>to the tests e.g. some container or virtual-machine based setups.</div><div></div><div></div><div>For releases of Firefox 89.0 and earlier Marionette will only be enabled in</div><div></div><div>GeckoView based applications when the Firefox preference</div><div></div><div>devtools.debugger.remote-enabled is set to true via</div><div></div><div>moz:firefoxOptions.</div><div></div><div></div><div></div><div></div><div></div><div></div><div>Marionette will only be enabled in GeckoView based applications when the</div><div></div><div>Firefox preference devtools.debugger.remote-enabled is set to True via</div><div></div><div>moz:firefoxOptions. This will be fixed in the Firefox 90 release for Android.</div><div></div><div></div><div>geckodriver is not yet feature complete. This means that it doesnot yet offer full conformance with the WebDriver standardor complete compatibility with Selenium. You can track theimplementation status of the latest Firefox Nightly on MDN.We also keep track of known Selenium, remote protocol, andspecification problems in our issue tracker.</div><div></div><div></div><div>Support is best in Firefox 57 and greater, although generally the morerecent the Firefox version, the better the experience as they havemore bug fixes and features. Some features will only be availablein the most recent Firefox versions, and we strongly advise using thelatest Firefox Nightly with geckodriver. Since Windows XP supportin Firefox was dropped with Firefox 53, we do not support this platform.</div><div></div><div></div><div>Starting with the 0.26.0 release geckodriver is able to connectto Android devices, and to control packages which are based on GeckoView(eg. Firefox Preview aka Fenix, or Firefox Reality). But it also stillsupports versions of Fennec up to 68 ESR, which is the last officiallysupported release from Mozilla.</div><div></div><div></div><div>This is happening on a headless machine, so I had not noted it before, but I have realized that despite the complaint that firefox and/or geckodriver are missing, a firefox window is opened on this machine! (and bokeh is not even caring to close ti afterwars)</div><div></div><div></div><div>E.g. it would help to know what combination of firefox&gecko or chromium-browser+chromedriver was attempted, including which one resulted in not being a valid executable. Of course the user need to figure it that is because software is not installed or not in path.</div><div></div><div></div><div>Why only for Firefox do we have to download/configure this driver? - It is not only Firefox but also for Google Chrome & MS Internet Explorer to work with Selenium 3.4.0 you need to mandatory download gecko driver v0.16.0 (or above) from this location or Chrome driver or IEDriverServer and save it in your machine. Upgrade your Mozila Firefox or Google Chrome or MS Internet Explorer to the latest stable version. Use the absolute path of the geckodriver/chromedriver/iedriver in your code while System.setProperty as follows:</div><div></div><div></div><div>Marionette as automation driver in Firefox supports a custom socket protocol, which is not compatible with the WebDriver specification. As such geckodriver needs to be used which acts as a proxy between Selenium and Firefox. Implemented as a small HTTP server it accepts commands which are conforming to the WebDriver specification, and forwards those to Marionette. Same applies to responses from Marionette which are getting transformed back into a WebDriver compatible HTTP response.</div><div></div><div></div><div>When running a test script in Selenium, the geckodriver.exe file must be used to implement the WebDriver protocol. Compatibility is the main benefit of utilizing GeckoDriver over the built-in Firefox driver. GeckoDriver and Selenium communicate using the W3C WebDriver protocol. The universally accepted Web Driver standard is W3C. This trait of GeckoDriver is highly beneficial to developers since it makes the tests more consistent across browsers and stable.</div><div></div><div></div><div>geckodriver.exe launches a local server that can be used to execute test scripts. By acting as a proxy, interfacing with Selenium, and translating requests into Marionette automation protocol. GeckoDriver establishes communication between Selenium and the Firefox browser.</div><div></div><div></div><div>Step 2: Unzip the file and obtain geckodriver.exe. This executable file needs to be accessible when running a program with Selenium, and there are three possible methods to accomplish this task.</div><div></div><div></div><div>Step 2: Options is a concept that was added to Selenium in order to allow the user to customize the Firefox session. In this example, it is used to provide the binary location of firefox.exe.</div><div></div><div></div><div>Since geckodriver is an executable, I concluded that it should be provided by the installation of the selenium package via pip or at least error out with some message stating what I need to do next. Apparently not, so I dug further: I thought that perhaps Ubuntu should have a package that provides the geckodriver executable so I used apt-file search geckodriver to search for it and found no results.</div><div></div><div></div><div>It's pretty straightforward. It searches my OS's PATH var and looks for geckodriver, assuming that it's in the current working directory if not found in PATH. In my tests, I made sure that it was found in my PATH variable. When I run my code, I get the following Traceback error:</div><div></div><div></div><div>Note: Don't use the latest geckodriver -- you need to pick the one that matches your version of Firefox. This is hard because the geckodriver release notes aren't consistent about saying which version of Firefox and Selenium they're compatible with.</div><div></div><div></div><div>"The path to the driver executable must be set by the webdriver.gecko.driver system property"Why would it all of a sudden start asking for geckodriver if it wasn't needed before? We haven't changed anything on the server or test machines. Test machines are running FF 46.0.1 on Windows 8.1. Trying to get to the bottom, we downloaded geckodriver.exe and copied to the FF directory, also added the directory path to the path environment variable.Now it throws the following error which we cant get past from:"Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure. Build info: version: 'unknown', revision: '31c43c8', time: '2016-08-02 21:57:56 -0700' System info: host: 'JR-win8-64-2', ip: '10.0.0.4', os.name: 'Windows 8.1', os.arch: 'x86', os.version: '6.3', java.version: '1.8.0_65' Driver info: driver.version: FirefoxDriver"Cant even get the Amazon test project to run as it throws the same error. We have also tried on FF 44 and 48, same results. Any assistance would be greatly appreciated.</div><div></div><div></div><div></div><div> df19127ead</div>
--- Synchronet 3.21a-Linux NewsLink 1.2