Timeout in RubyMine's Evaluate Expression window when running selenium-webdriver commands (Ruby 2.3.x)

[ruby-debug]

Timeout in RubyMine's Evaluate Expression window when running selenium-webdriver commands (Ruby 2.3.x)

[denofevil]

This seems to be caused by introduction of 60s @open_timeout in http.rb. It used to be nil, so no additional threads were spawned. Now, with 60s it spawns a new thread, which cannot run as the process is stopped on the breakpoint, so it timeouts there.

Minimal case would look like this:

require 'timeout'

def compute_with_timeout
  Timeout.timeout(10) { Thread.list }
end
with = compute_with_timeout #breakpoint here
puts with

[stevegibson]

Per this stackoverflow question, this is also happening with Watir-webdriver.

[luke-hill]

Sorry to bump a really old thread. Did this get anywhere?

[xenjke]

class OverrideDriver < Selenium::WebDriver::Remote::Http::Default
  def http
    client = super
    client.open_timeout = 0
    client
  end
end

# when creating driver instance
Watir.new(:chrome, http_client: OverrideDriver.new)

that solves the issue for me

[luke-hill]

@xenjke Are you using Se3+?

[xenjke]

@luke-hill 3.4.0 it is

[xenjke]

@luke-hill another workaround mentioned in https://youtrack.jetbrains.com/issue/RUBY-17930#comment=27-1794364 is to monkeypatch the Timeout module for debugging purposes only.

Do not use that on production.

module Timeout
  def timeout(sec, klass=nil)
    yield(sec)
  end
  module_function :timeout
end

[xenjke]

came up with

if $LOADED_FEATURES.any? { |f| f.include? 'debase' }
  module Timeout
    def timeout(sec, klass=nil)
      yield(sec)
    end

    module_function :timeout
  end
end

[luke-hill]

@xenjke The original one works when I implement it as written (I tried a slightly shorter version).

I'd rather know why this has happened. I had a look at the docs and I have traced the file in RubyMine, but as I'm using Se2.53 I'm not sure why this is happening.

Either way your fix works, I just hope RubyMine fix it up their end if possible

[luke-hill]

This issue can be closed as fixed.

For readers: Use at least RubyMine 2017.2.x+ and either
Ruby 2.2
or
Ruby 2.3+ and Selenium 3.0.7+

[valich]

@luke-hill There is still an issue with incorrect thread usage for timeout, #128 should make ruby use another thread for evaluation. It's targeted to 2018.1