So, we’ve just pushed another update to RubyMine 3.2 — version 3.2.2. You can download it from our web site.
There are not so many changes, but all are quite important. Our main goal was to fix the most critical IDE performance and gems management issues. See the full list of changes.
We are sorry if you had problems with RubyMine 3.2. Thanks for you patience and we hope they are resolved now with this update.
Also we receive reports that RubyMine works fine on the fresh Mac OS X 10.7 “Lion” released yesterday by Apple. You just need to download Java runtime, which the operating system suggests and does automatically.
Develop with pleasure!
The JetBrains RubyMine Team
Good job! I still have the “Failed to load remote gems http://gems.rubyonrails.org” error but CPU seems ok for now
Argh, scanning for gem requirements is till there
The code reformatting is fixed. You guys rock!
Scanning for gem requirements still there.
When a file is open, the “eye” remains visible all the time, without ever turning Green, Amber or Red.
CPU is still going 50%, 60%, 70% and fall again to 5-6%, and then again the same. Like a never ending cycle.
The only improvement is that IDE does not freeze anymore.
I also confirm the existence of the “Failed to load remote gems http://gems.rubyonrails.org” error” (3 times), with no obvious reason, when the Rails project opens.
Why the size is less than half it was before ?
Nice! But what changed ?
Thanks
Someone should test how rubymine works on the new MacBook Air i7. I would switch my laptop in an instant if it is fast enough
@erwann, @Ilias please see https://github.com/rubygems/gemcutter/issues/319 for “Failed to load remote gems” issue. “Scanning for gems” is should only happen when editing Gemfile
I am also observing this: When a file is open, the “eye” remains visible all the time, without ever turning Green, Amber or Red.
CPU is still going 50%, 60%, 70% and fall again to 5-6%, and then again the same. Like a never ending cycle.
I addition to that, code analysis never completes so things like “Go to definition” do not work.
Re: stuck inspections reported above: I was able to clear this out by removing RM cached data with ‘rm ~/.RubyMine32/system -rf’. After that, it was able to complete the process and now works as normal.
Performance is worse than 3.2.1 for me. Beach balls abound, mostly when I try to open a context menu. Possibly worst in specs.
Command-clicking on classes is broken in 3.2.2 (on Mac OS X 10.6.8).
I’m not sure RubyMine really is Lion compatible. Code inspection is not working for Ruby code and I see the following error repeated in the rubymine log:
2011-07-21 19:15:38,304 [ 24220] ERROR – aemon.impl.PassExecutorService – Failed to bind stub to AST for element class org.jetbrains.plugins.ruby.ruby.lang.psi.impl.variables.fields.RInstanceVariableImpl in /Users/drew/.rvm/rubies/ruby-1.8.7-tv1_8_7_174/lib/ruby/1.8/test/unit/util/observable.rb
File stub tree:
com.intellij.psi.stubs.PsiFileStubImpl@1bdcfef
org.jetbrains.plugins.ruby.ruby.lang.psi.stubs.impl.RCallStubImpl@9e6c65
RModuleStub:Test
RModuleStub:Unit
RModuleStub:Util
RModuleStub:Observable
org.jetbrains.plugins.ruby.ruby.lang.psi.stubs.impl.RConstantStubImpl@de8750
RMethodStub:add_listener
org.jetbrains.plugins.ruby.ruby.lang.psi.stubs.impl.RConstantStubImpl@185b361
org.jetbrains.plugins.ruby.ruby.lang.psi.stubs.impl.RConstantStubImpl@c3da5f
org.jetbrains.plugins.ruby.ruby.lang.psi.stubs.impl.RConstantStubImpl@35d1f0
org.jetbrains.plugins.ruby.ruby.lang.psi.stubs.impl.RConstantStubImpl@16a0cb3
RMethodStub:remove_listener
org.jetbrains.plugins.ruby.ruby.lang.psi.stubs.impl.RConstantStubImpl@167fc18
org.jetbrains.plugins.ruby.ruby.lang.psi.stubs.impl.RConstantStubImpl@1d7ab26
RMethodStub:notify_listeners
RMethodStub:channels
org.jetbrains.plugins.r …
Loaded file AST:
Ruby file
PsiComment(line comment)(‘#–’)
PsiComment(line comment)(‘#’)
PsiComment(line comment)(‘# Author:: Nathaniel Talbott.’)
PsiComment(line comment)(‘# Copyright:: Copyright (c) 2000-2002 Nathaniel Talbott. All rights reserved.’)
PsiComment(line comment)(‘# License:: Ruby license.’)
Compound statement
Ruby:Call
Identifier
PsiElement(identifier)(‘require’)
List of expressions
Single quoted like string
PsiElement(single quoted like string beginning)(”’)
PsiElement(string content)(‘test/unit/util/procwrapper’)
PsiElement(string end)(”’)
PsiElement(end of line)(‘n’)
Ruby:Module
PsiElement(module)(‘module’)
Name
Ruby:Class Name
PsiElement(constant)(‘Test’)
PsiElement(end of line)(‘n’)
Body statement
Compound statement
Ruby:Module
PsiElement(module)(‘module’)
Name
Ruby:Class Name
PsiElement(constant)(‘Unit’) …
the code completion is not working anymore, when I press ctrl + space it doesn’t give me any option for completing the code as it was doing before
Great bugfix :/
Code completion – not working
Documentation lookup – not working
Go to declaration/definition – not working
Great work guys! :/
3.2.2 is totally unusable for me. freezes way too often. went back to 3.2.1.
@Drew, @marc, @Krzysztof, @Ahto, please send me your idea.log (Help | Reveal log in …) to dennis.ushakov at jetbrains.com
Does running File | Invalidate caches help?
I think the invalidation worked. doesn’t freeze when trying to do code completion or Go to declaration/definition. Testing some more soon.
Thanks for the tip.
Not sure where the best place to ask this (I’ve tried tweeting @rubymine, but no reply as of yet).
How can I configure generations to automatically add to Subversion (or another VCS) so I can commit them straight away?
I can confirm it works on Lion. It would be great if it supported Lion full screen mode, that would rock.
Invalidating the cache completely fixed the problem, thanks guys! No more java errors and code completion / documentation lookup / Go to declaration/definition is all working again.
Netbeans user looking to switch to RubyMine following OS X Lion install. Holding off purchase until I see these issues are resolved!
Reverting back to 3.2.1 did not fix the code completion problem for me. Has anyone else figured out a way around this?
My license key doesn’t work anymore on 3.2.2. I bought it in December 2010, for RubyMine 3.0.
Still no recognition & syntax-highlighting of localized cucumber-features…
————————————————–
# language: de
# encoding: utf-8
Funktionalität: Tolle Funktionalität
————————————————–
*Hmpf*
Still get this errors (3 times):
Failed to load remote gems
/Users/rafael/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:166: stack level too deep (SystemStackError) Please check proxy settings and gem urls
same problem here: Failed to load remote gems http://gems.rubyonrails.org
Code completion inside SASS files does not work in 3.2.2 even after invalidating caches. Does work in 3.1.x on the same file.
I also got this.. Errors (3)
Failed to load remote gem Stack level too deep
Nice that the most aggravating performance problems from 3.2 was fixed. I still get freezes but far less frequent than with 3.2.1.
With the latest version, 107.466, I still get the stack level too deep (SystemStackError) error but only on Ruby 1.9.2p180. I found this out accidentally when I, for other reasons, backed my project out from Ruby 1.9.2 back to Ruby 1.8.7. Under 1.8.7, everything works fine.
Other details you might be interested in:
osx 10.6.8
java version 1.6.0_26
Java(TM) SE Runtime Environment (build 1.6.0_26-b03-384-10M3425)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02-384, mixed mode)
I’m getting the “stack level too deep” problem as well, and with 1.9.2p180. I found this page via Google of that message, and was hoping to read that 3.2.2 fixed it. Instead the hit shows it hasn’t been resolved.
Yup. Me too. I’m getting the “stack level too deep” problem as well, and with 1.9.2p180.
Congrats, looks like another stream of improvements.
It’s freezing when I use GoTo definition, though.
The SystemStackError is a bug in RubyGems under Ruby 1.9. It was fixed in RubyGems 1.8.6 released on 2011-07-25. To get it run:
gem update –system
More at:
http://stackoverflow.com/questions/6760867/failed-to-load-remote-gems-stack-level-too-deep-systemstackerror
Turadg, I get
gem update –system
Updating installed gems
Nothing to update
then the “stack level too deep” problem as well with 1.9.2p180.
The correct command to be issued is:
gem update —system
Works as expected, notice the double hyphen.
Somehow the blog commenting system is removing the double hyphen from the gem update command…
Yep, I confirm Bruno’s tip (tnx, Bruno!):
This is a new problem with Ruby 1.9.2 (I have 1.8.7 in parallel and when I switch forth and back with “pik” between those versions, it is only 1.9.2 causing that error message).
I issued a “gem update –system” (with two “-” that is) and magic -it works!
Got it working but I’m still getting a few freezing errors…