Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to run Rubocop #3248

Closed
coding-red-panda opened this issue Jun 27, 2016 · 7 comments
Closed

Unable to run Rubocop #3248

coding-red-panda opened this issue Jun 27, 2016 · 7 comments

Comments

@coding-red-panda
Copy link

I just upgraded Rubocop to the latest version, but when I try to run it now, I receive the error:

➜  bundle exec rubocop
Error: Unknown Ruby version 0.0 found in `.ruby-version`.
Known versions: 1.9, 2.0, 2.1, 2.2, 2.3

This behaviour started after the upgrade.

Expected behavior

I expect Rubocop to work

Actual behavior

It spits out this error. Worked fine before the upgrade.

Steps to reproduce the problem

Have Ruby 2.2.5 installed, and upgrade from 0.40.0 to 0.41.1
Then use the command bundle exec rubocop --auto-gen-config or just bundle exec rubocop
Running the -V command works for some reason.

RuboCop version

$ rubocop -V
0.41.1 (using Parser 2.3.1.2, running on ruby 2.2.5 x86_64-darwin15)
@coding-red-panda
Copy link
Author

Update

Our .ruby-version file originally contained the value ruby-2.2.5.
When I switched this 2.2.5 it suddenly worked fine.

@bquorning
Copy link
Contributor

Seems to be caused by #3228 - cc/ @pclalv

@bbatsov
Copy link
Collaborator

bbatsov commented Jun 27, 2016

If rbenv supports both notations, I guess we should support them as well.

@aviflax
Copy link

aviflax commented Jun 28, 2016

I’m having the same problem, but I’m using JRuby, so my prefix in .ruby-version is jruby. It doesn’t seem like #3251 will fix the problem for JRuby users.

@achiinto
Copy link

achiinto commented Jul 4, 2016

We have our own build of Ruby, which is basically the same copy of Ruby as publicized, Just due to enterprise security reason, we ended up with our own and have a different naming. So, this bug is preventing it to work.

@bquorning
Copy link
Contributor

@achiinto I believe #3261 will fix the problem?

@achiinto
Copy link

achiinto commented Jul 5, 2016

hi @bquorning, seems like that will fix it. Thanks

Neodelf pushed a commit to Neodelf/rubocop that referenced this issue Oct 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants