You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the release of geckodriver version 0.21.0 the keep-alive mode is supported, with the caveat (mozilla/geckodriver#1304) that the timeout on the server side is set to only 5s. As result any command will fail which is send after a time.sleep() larger or equal to 5s. Here an example:
As a workaround, for the moment, I force the webdriver not to use keep_alive connection.
ie :
selenium/webdriver/firefox/webdriver.py line 165 executor = FirefoxRemoteConnection(remote_server_addr=self.service.service_url, keep_alive=False)
I know that @AutomatedTester rewrote that part of the Python bindings to make use of urllib3, but the patch doesn't seem to have landed yet. David, can you please give us an update?
Meta -
OS: All
Selenium Version: 3.13.0
Browser: Firefox
Browser Version: All versions of Firefox
Since the release of geckodriver version 0.21.0 the keep-alive mode is supported, with the caveat (mozilla/geckodriver#1304) that the timeout on the server side is set to only 5s. As result any command will fail which is send after a
time.sleep()
larger or equal to 5s. Here an example:Expected Behavior -
The Selenium client has to check for a valid and active connection before sending the request. It shouldn't result in an exception as shown below.
Actual Behavior -
The next command after the 5s delay will fail with:
The text was updated successfully, but these errors were encountered: