Rubocop returns empty output
See original GitHub issueI’m experiencing what to me seems like a very weird issue. Whenever the extension runs, I get this message on VS Code:
command /Users/X/.rbenv/shims/rubocop returns empty output! please check configuration
The error seems clear enough but… if I run the exact same command in the command line, I get a proper output. I’ve tried making some tweaks to the configurations, namely the execution path, using bundle or not, but nothing seems to solve it. I’ve dived in the code to see where this message was being given and this supposedly only happens if the output of the command is indeed empty, so I’m not sure what’s going on. Could I do something to see exactly what command is running to try and debug it?
Anyone experienced the same?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:43
- Comments:19
Top Results From Across the Web
Error on config Rubocop for VSCODE in WSL2
When I try to execute: command /home/joao/.rbenv/shims/rubocop returns empty output! please check configuration. and ...
Read more >rubocop returns empty output! please check configuration.
After updating vscode, I started receiving this error message /Users/xx/.rbenv/shims/rubocop returns empty output! please check ...
Read more >Fixing VS Code Rubocop Issues - Simon Online
The issue here was that the rubocop in the project was newer than the globally installed rubocop so it was returning empty output....
Read more >VS Code x Rubocop - ruby_executable_hooks: No such file or ...
/Users/lynnbright/.rvm/gems/ruby-2.6.6/bin/rubocop returns empty output! please check configuration. env: ruby_executable_hooks: No such ...
Read more >Basic Usage :: RuboCop Docs
rubocop --only Rails/Blank,Layout/HeredocIndentation,Naming/FileName ... Only output offense messages at the specified --fail-level or above.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I Replace
bin
in the PATH withwrappers
and solved the issue: vscode setting:ruby.rubocop.executePath": "/Users/USER_NAME/.rvm/gems/ruby-2.6.5/wrappers/
Just in case this helps anyone, I had a bad
.rubocop.yml
file in my home folder (/Users/myusername/.rubocop.yml
) that was being loaded as part of the stack. Deleting it, so rubocop only used the project’s own config, fixed it for me. Such a dumb fucking issue I’ve had for years, now finally dealt with. I am in ecstasy