Usage of invalid driver causes an endless execution? about thirtyfour

[stevepryde]

Added note about timeout in WebDriver::new

[stevepryde]

Is this the case even if you specify a timeout? Does chromedriver send a response?

[zhiburt]

Does chromedriver send a response?

No

Is this the case even if you specify a timeout?

How I suppose to do it?

This is how I configure the driver.

            let mut cops = DesiredCapabilities::firefox();
            cops.set_headless()?;
            // by this option we try to resolve CAPTCHAs
            cops.add("unhandledPromptBehavior", "accept")?;

            if let Some(p) = cfg.proxy.as_ref() {
                let proxy = convert_proxy(p);
                cops.set_proxy(proxy)?;
            }

            WebDriver::new(cfg.webdriver_address.as_str(), &cops).await?

[stevepryde]

There is a new_with_timeout constructor which allows you to specify a timeout.

[zhiburt]

new_with_timeout works 👍

error sending request for url (http://localhost:4444/session): operation timed out\n

Maybe it's worth mentioning in Webdriver::new about this behavior?

[stevepryde]

I'm going to change new() to default to a 120 second timeout. Users can call new_with_timeout(..., None) if they want no timeout.