Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error on parsing output (It might non-JSON output) : ""

See original GitHub issue

After the latest update I get this error every time rubocop is run.

Warn: Error on parsing output (It might non-JSON output) : ""

Issue Analytics

State:
Created 7 years ago
Reactions:4
Comments:24 (3 by maintainers)

Top GitHub Comments

11reactions

robertocortizcommented, Jun 22, 2016

@tophattom I’m curious what configuration setting did you have to fix to get this to go away?

3reactions

cesmoakcommented, Jul 10, 2016

I got rid of this error as soon as I specified a rubocop config file in the extension settings ("ruby.rubocop.configFilePath": "<something>") and ensured that that file actually existed (an empty file is fine).

Top Results From Across the Web

ruby - Why i get Error on parsing output (It might non-JSON ...

The solution was to run rubocop from the command line and correct enough offenses until it was manageable by the extension. I used...

Error on parsing output (It might non-JSON output) : "" -

After the latest update I get this error every time rubocop is run. Warn: Error on parsing output (It might non-JSON output) :...

Couldn't parse output from RuboCop. See the ... - YouTrack

Whenever I try and and select "Autocorrect issue" for any Rubocop errors, the Event Log prints the following: "RuboCop Error: Couldn't parse output...

[PDK-1680] Rubocop config errors are not displayed in the ...

In terms of "a better way than parsing stdout" I meant if the output in other formats is more suitable to my use-case...

Error while parsing JSON Response in REST API Post call

I was able to resolve the issue. I had forgotten to append "?format=json" at the end of the REST url. So it was...