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

Breaks when a .rubocop directory exists #3423

Closed
joejuzl opened this issue Aug 18, 2016 · 0 comments
Closed

Breaks when a .rubocop directory exists #3423

joejuzl opened this issue Aug 18, 2016 · 0 comments
Labels

Comments

@joejuzl
Copy link
Contributor

joejuzl commented Aug 18, 2016

Rubocop errors when there is a directory named .rubocop

Expected behavior

Use the .rubocop.yml config

Actual behavior

Is a directory @ io_fillbuf - fd:7 .rubocop
/Users/joejuzl/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/rubocop-0.42.0/lib/rubocop/options.rb:38:in `readlines'
/Users/joejuzl/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/rubocop-0.42.0/lib/rubocop/options.rb:38:in `args_from_file'
/Users/joejuzl/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/rubocop-0.42.0/lib/rubocop/options.rb:19:in `parse'
/Users/joejuzl/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/rubocop-0.42.0/lib/rubocop/cli.rb:24:in `run'
/Users/joejuzl/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/rubocop-0.42.0/bin/rubocop:14:in `block in <top (required)>'
/Users/joejuzl/.rbenv/versions/2.2.3/lib/ruby/2.2.0/benchmark.rb:303:in `realtime'
/Users/joejuzl/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/rubocop-0.42.0/bin/rubocop:13:in `<top (required)>'
/Users/joejuzl/.rbenv/versions/2.2.3/bin/rubocop:22:in `load'
/Users/joejuzl/.rbenv/versions/2.2.3/bin/rubocop:22:in `<main>'

Steps to reproduce the problem

Run rubocop in a directory with a sub-directory named .rubocop.

RuboCop version

$ rubocop -V
0.42.0
@bbatsov bbatsov added the bug label Aug 24, 2016
joejuzl pushed a commit to joejuzl/rubocop that referenced this issue Aug 31, 2016
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
Projects
None yet
Development

No branches or pull requests

2 participants