Project
Ruby
Priority
Critical
Type
Usability Problem
Fix versions
RubyMine 1.1.1
State
Fixed
Assignee
Roman Chernyatchik
Subsystem
Run Configurations
Affected versions
No Affected versions
Fixed in build
108.101  
  • Created by   Menno
    2 years ago (22 May 2009 01:27)
  • Updated by   Vadim Gurov
    8 months ago (18 May 2011 18:18)
  • Jira: RUBY-4094
    (history, comments)
 
RUBY-4094 Cannot disable --drb and --backtrace options in RSpec config
0
Issue is visible to: All Users
  The issue is visible to the selected user group only
In a Ruby project I create an RSpec run config. By default it has the "Run with DRB server" and "Output full bactrace" (notice the bactrace typo by the way) enabled.
Starting the test fails with "No server is running", which makes sense.
When I disable the DRB option in the run config dialog, the test is still started with –drb. And the option is enabled again when re-opening the config. Same goed for –backtrace.

It seems unticking the DRB and backtrace checkboxes has no effect.

Looking for a workaround, I considered starting a DRB server, but this option is not listed in the Tools menu (because it's a Ruby project?)

Environment: Sun JDK 1.6.0_13 on Ubuntu Linux 9.04 x86_64
Ruby 1.8.7 or JRuby 1.20 (same bug with both SDK's)

Issue was resolved
Comments (8)
 
History
 
Linked Issues (?)
 
Roman Chernyatchik
  Roman Chernyatchik
22 May 2009 21:31
2 years ago
Please check this on coming RubyMine 1.1 RC. It seems we've fixed this. Actually –drb option will be selected only if drb server is running in background. Unfortunately due to bug in UI this option is initialized incorrectly.
Menno
  Menno
02 Jun 2009 13:59
2 years ago
Retested with release 1.1 / 952. The only difference I see compared to 907 is that the "Use DRb server" option is greyed out so it can't be changed. It is enabled initally and cannot be disabled. No server is running (nor can be started via the tools menu), so running the specs still fails in the same way.
Roman Chernyatchik
  Roman Chernyatchik
02 Jun 2009 14:29
2 years ago
Hello Menno,

Our fix works for new configurations and doesn't fix existing configurations. Please recreate that configuration. If Drb server isn't running new configuration will be created with unselected "use drb" option also during editing configuration settings checkbox will be disabled. Also may be use saved selected drb option in default settings (see RubyMine | Run | Edit Run Configuratins.. | Edit Defaults button )?
Menno
  Menno
02 Jun 2009 14:45
2 years ago
Threw away all configurations and restarted RubyMine. Now choose menu Run - Edit configurations. (List of configurations is empty.).

When I now click "Edit defaults" and select RSpec, the DRb server option is selected and greyed out.

Same when I do an "Add new configuration".
Menno
  Menno
02 Jun 2009 14:45
2 years ago
Note that this is not a Rails project, plain (j)ruby.
Roman Chernyatchik
  Roman Chernyatchik
02 Jun 2009 15:14
2 years ago
I know some trick that will help you. Open any rails project with rspec drb server script ( or create new project and initialize rspec support). Run drb server, than open "Edit Default" dialog and remove option from "drb server".

It seems it was bad idea to forbid changing Drb option when server isn't launched. In next version this option will be always enabled for selection/deselection.
Menno
  Menno
03 Jun 2009 14:43
2 years ago
Somehow the Rails project route didn't work out. Setting DRB false in the workspace.xml solved the problem though. Hooray for non-binary confg files :-)
Roman Chernyatchik
  Roman Chernyatchik
24 Jun 2009 13:17
2 years ago
done. "-drb" option will be always editable