-
Notifications
You must be signed in to change notification settings - Fork 215
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
fix bugs with plugin parsing #216
Conversation
c5a7325
to
c40946e
Compare
ready for review @ransombriggs |
if err != nil { | ||
return nil, fmt.Errorf("Error reading plugin: %s\n%s\n%s", name, err, string(output)) | ||
return nil, fmt.Errorf("Error reading plugin: %s\n", name) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dickeyxxx why did you remove err
from the Error reading plugin
string?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh I guess I can include that part
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
c40946e
to
a0586f5
Compare
If the plugin fails to parse it formerly would just exit silently and all plugins would fail to install. Also, if the plugin output anything on stderr it would try to parse it and also fail. This redirects stderr out to the terminal and shows the parsing error if any.
@dickeyxxx lgtm |
* Adjust 'heroku releases' output to fit terminal width * Trigger CI
If the plugin fails to parse it formerly would just exit silently and
all plugins would fail to install.
Also, if the plugin output anything on stderr it would try to parse it
and also fail.
This redirects stderr out to the terminal and shows the parsing error if
any.