Stuck at indexing RubyMine.app/rubystubs18/not_implemented_error.rb

When I open a project and RubyMine starts indexing, it gets stuck at RubyMine.app/rubystubs18/not_implemented_error.rb.

It actually succesfully indexes my own project but get stuck when trying to index this particular file.

8 comments

Hi,

could you please try to invalidate caches and see if this helps (File|Infalidate caches)
If it is not please provide RubyMine's log file (Help|Show Log in ...)

Regards, Oleg.

0

Unfortuntely, invalidating the cache didn't work.
I've attached one of the log files.

I attempted to 'avoid' this file by renaming the entire rubystubs18 folder, but it still get stuck while indexing some other files.
So I suspect the problem doesn't lie with the files RubyMine is attempting index.



Attachment(s):
threadDump-20140106-152440.txt.zip
0

It looks like a bug in our ruby parser but I'm surprised I've not see it before :(
What version of RubyMine are you using?

Regards, Oleg.

0

Hi, my RubyMine version is 5.4.3.2.1.

I also noticed that this issue only happens with my current rails project, but if I create a brand new rails project, no issues.

0

Hi,

I do not remember suh problem with 5.4.3.2.1 :(  Either it was fixed long time ago or it is not about one of our stub files.
And I do not see the problem with 6.0.  So (if it is possible) I'd suggest to try 6.0.2 and see if the problem is reproduible there.
Also I wonder how you have identified that the problem is caused by indexing of the stub file?  Could you try to remove it and see it the problem
will be fixed?

Regards, Oleg.

0

Hi Oleg

I've just tried 6.0.2 and it works !

But I'm still not sure what is going on with 5.4.3.2.1.
Initially, I thought the problem was caused by the stub file because the indexing status window showed that the indexing got stuck at that particular file.
However, after I renamed the entire rubystubs18 folder and restarted RubyMines, indexing got stuck at another file.
So my guess is that the issue has nothing to do with rubystubs19/not_implemented_error.rb.

0

Most likely the problem is caused by one of your files and RM's notifications just confuse you.

Oleg.

0

Please sign in to leave a comment.