rubocop returns empty output! please check configuration.
See original GitHub issueAfter updating vscode, I started receiving this error message
/Users/xx/.rbenv/shims/rubocop returns empty output! please check configuration.
If I do bundle exec rubocop file_name
rubocop will work.
I have these in the configuration file.
"ruby.rubocop.executePath": "/Users/xx/.rbenv/shims/",
"ruby.rubocop.configFilePath": "/Users/xx/projects/mp/.rubocop.yml",
any idea, please!
Issue Analytics
- State:
- Created 2 years ago
- Reactions:15
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Rubocop returns empty output · Issue #113 - GitHub
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 ...
Read more >Error on config Rubocop for VSCODE in WSL2 - Stack Overflow
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 >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
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
@marlonguimaraes
Most of the time when it happens when you update rubocop in your gemfile.lock, but vscode hasn’t been reloaded since then (just happened to me, I never close vscode)
Make sure you ran
bundle
to update dependencies, make sure you don’t have any pending update on vs codeThen hard reload vs code (quit + re-start), and it’s gone
I have RuboCop installed globally (i believe).
This VSCode notification pops up when I clone into a project that does not have rubocop in the gemfile.
I add Rubocop to the project by running
bundle add rubocop
and it seems to satisfy the angry little popups from VSCode.