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

Output exception details to STDERR #152

Conversation

jpignata
Copy link
Contributor

When an exception occurs when running a check, output debugging details
about the exception to STDERR.

The Code Climate kitbit engine wraps kibit and emits issues in JSON
for each check on STDOUT. Any unexpected content on STDOUT causes the
engine run to fail as debugging information is expected on STDERR.
This small patch moves the output of debugging information to to
STDERR.

When an exception occurs when running a check, output debugging details
about the exception to STDERR.

The Code Climate kitbit engine wraps kibit and emits issues in JSON
for each check on STDOUT. Any unexpected content on STDOUT causes the
engine run to fail as debugging information is expected on STDERR.
This small patch moves the output of debugging information to to
STDERR.
@danielcompton
Copy link
Member

To clarify, you only want Kibit analysis results on STDOUT, and everything else on STDERR? https://github.com/jonase/kibit/blob/0fd16aee8037db09cfb9e6d27be31dad17f14e3f/src/kibit/reporters.clj prints to STDOUT, but I don't think that's a problem here?

@jpignata
Copy link
Contributor Author

@danielcompton That's correct. We expect reports to print to STDOUT, but other debugging details such as exception details to print to STDERR.

danielcompton added a commit that referenced this pull request Feb 29, 2016
…tions

Output exception details to STDERR
@danielcompton danielcompton merged commit be013ef into clj-commons:master Feb 29, 2016
@danielcompton
Copy link
Member

Cool, merged :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants