-
Notifications
You must be signed in to change notification settings - Fork 68
rubocop returns empty output! please check configuration. #132
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
Comments
seems to be caused by
|
same with rubocop 0.92.0 |
I get this error everytime i save a ruby file. Also formatting a ruby file does not work because of this error. rubocop: 0.92.0 |
I'm still seeing this message and I set up my settings.json to point to /home/jmstump/.rbenv/shims/ Rubocop runs in other editors so it seems to be either related to the extension or my setup of it. |
I see it pop time to time since some days also, my guess is that there is something that broke again, but it's not consistent on my machine (depend on the content of the file itself and the rubocop version is seems) If you find a way to 100% reproduce it would be glad to help and try find what is missing |
@ngouy I ended up disabling linting in ruby altogether because a recent update broke it while using live share (basically the only reason I use VSCode). I'll see if I can give it another try and get you some more information. |
Just started getting this pop up after the last VSCode update (1.55.0) |
I am a bit underwater rn and it works for me so ... Will probably check it out when it will break for me and it makes me loses time. Sorry guys For the live share it's way out of my reach, sorry |
I tried several solutions and I was only able to solve the problem by removing the visual code via flatpak and downloading the .deb. |
This worked for me according this post:
|
rubocop gem version 0.80.1
At the command line I do a which rubucop and get my path:
It works fine. If I paste that into the User and Workspace settings for the path:
I get the error rubocop returns empty output! please check configuration.
I am not sure why this is. This extension seems unable to activate rubocop correctly. What is typically wrong with configurations where you provide the correct path to the executable, but get empty output?
The text was updated successfully, but these errors were encountered: