ruby-debug-ide 0.7.0.beta4 always hangs on rubymine 2018.1

Trying to debug a single spec, the debugger open two listener and hangs forever.

Testing started at 16:30 ...
/Users/rd/.rvm/rubies/ruby-2.3.1/bin/ruby -e at_exit{sleep(1)};$stdout.sync=true;$stderr.sync=true;load($0=ARGV.shift) /Users/rd/.rvm/gems/ruby-2.3.1/gems/ruby-debug-ide-0.7.0.beta4/bin/rdebug-ide --disable-int-handler --evaluation-timeout 10 --evaluation-control --time-limit 100 --memory-limit 0 --rubymine-protocol-extensions --port 57040 --host 0.0.0.0 --dispatcher-port 57041 -- /Users/rd/.rvm/gems/ruby-2.3.1/bin/rspec /Users/rd/src/myproject/spec/services/booking_service_spec.rb --require teamcity/spec/runner/formatter/teamcity/formatter --format Spec::Runner::Formatter::TeamcityFormatter
Fast Debugger (ruby-debug-ide 0.7.0.beta4, debase 0.2.2, file filtering is supported) listens on 0.0.0.0:57040
Fast Debugger (ruby-debug-ide 0.7.0.beta4, debase 0.2.2, file filtering is supported) listens on 0.0.0.0:57052

7 comments
Comment actions Permalink

This is happening for me too, using IntelliJ IDEA.  

The IDE tries to install ruby-debug-ide-0.7.0.beta3 if the gem is not installed.

Using 'gem install ruby-debug-ide --pre' installs ruby-debug-ide (0.7.0.beta4)

 

Both just hang when trying to debug a ruby test:

Fast Debugger (ruby-debug-ide 0.7.0.beta4, debase 0.2.2, file filtering is supported) listens on 0.0.0.0:53778
Run options: --name=test_admin_customer_mapping --seed 14110

# Running:

Fast Debugger (ruby-debug-ide 0.7.0.beta4, debase 0.2.2, file filtering is supported) listens on 0.0.0.0:53781



0
Comment actions Permalink

Hello,

could you please check how it goes in RubyMine 2018.1.1 with updated debug gems (there've been a similar problem already fixed).

0
Comment actions Permalink

I've downloaded the trial of rubymine and this works there.

However I've updated IntelliJ IDEA and still cannot debug tests there - still the same problem. Will there be an update for IntelliJ soon?

0
Comment actions Permalink

@Mike,

have you tried the last 2018.1.2 RC version with the updated Ruby plugin 2018.1.20180417?

 
0
Comment actions Permalink

Experienced the same problem but the 18.1.1 update fixed it for me. Thanks!

0
Comment actions Permalink

The 2018.1.2 RC fixed the issue for me too. Thank you :)

0
Comment actions Permalink

Hi,

The update to rubymine 2018.1.1 fixed the issue for me too, but it opened a new one. Generators don't work anymore. I'll open a new thread.

 

thanks

0

Please sign in to leave a comment.