-
Notifications
You must be signed in to change notification settings - Fork 29
ProcessNotCreatedException: Failed to run RuboCop command on RubyMine 8.0.3 and plugin 3.1.0 #34
Comments
Can you restart ruby mine to confirm that 3.1.0 is loaded properly? That bug should definitely not appear since I'm not adding "exec" anywhere anymore since 3.1.0 |
@sirlantis I have restarted the mac and the issue still persists. |
Btw, I switched to another rubygem project and I am getting the following IDE Fatal Error:
|
Opening the Gemfile ( or any other .rb ) produces the following in the idea.log:
|
Wow... this is two issues related to the command being executed. After switching back to the original project I get the original behaviour:
When I switch to the other project I mentioned I get the following error:
I can verify that the rubocop is installed and can be executed under terminal for both projects. Perhaps this issue is project related? |
I am also getting this on the same project I mentioned in Issue #30.
|
@sirlantis Happy new year! Is there any update on this? |
👍 |
@ikappas mind if I ask where you install your gems? I just spent a couple of days working with RM to get it to even see my gems and ended up with a strange solution. (I actually install my gems with bundler to a non-standard path Here's what I did:
yeah, starting RM inside the bundled environment... strange but it works. |
thanks @elskwid. |
Same for me, works only with |
3.1.0 plugin and RM 8.0.3 started from the project directory with |
Wow. I had "End of input at line 1 column 1" problem too (not the "Cannot run program "rubocop" problem). 8.0.3 / 3.1.0, Ubuntu. The exact command from the logs was showing that the rubocop was able to generate proper json. I tried everything and nothing helped until I tried |
Any update on fixing this? |
@danlaffan you can try my unofficial release on Pull-Request #39 |
Thank you! That worked for me on MacOS. |
@beder +1, thank you |
This is the similar/related issue with #30.
After re-inspecting the idea.log file I can see that rubocop is executed with the following command:
the test.rb path is the absolute path to the project file (Verified to be OK)
This command produces the correct output when run under terminal
@sirlantis As you mentioned this should be
bundler exec
@sirlantis I have modified this after the restart you suggested
The text was updated successfully, but these errors were encountered: