Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

[proxy] print all stderr output from callWeave to the proxy logs, even if successful #1067

Merged
merged 1 commit into from
Jul 4, 2015

Conversation

paulbellamy
Copy link
Contributor

Fixes #1056

@rade
Copy link
Member

rade commented Jul 3, 2015

We don't want to log what comes out of stdout. We want to log a warning when anything comes out of stderr.

@bboreham bboreham changed the title [proxy] print all output from callWeave to the proxy logs, even if successful [proxy] print all stderr output from callWeave to the proxy logs, even if successful Jul 3, 2015
if err != nil {
return nil, err
return nil, fmt.Errorf(string(stderr))

This comment was marked as abuse.

This comment was marked as abuse.

@rade rade assigned paulbellamy and rade and unassigned rade and paulbellamy Jul 3, 2015
@rade
Copy link
Member

rade commented Jul 3, 2015

It would be good to (manually) test this with the warning spat out by #1053, since that is what prompted filing of the issue.

@rade rade assigned paulbellamy and unassigned rade Jul 3, 2015
@rade
Copy link
Member

rade commented Jul 4, 2015

It would be good to (manually) test this with the warning spat out by #1053, since that is what prompted filing of the issue.

Have done this. All ok.

In future please create PR branches on weaveworks/weave.

rade added a commit that referenced this pull request Jul 4, 2015
print all stderr output from callWeave to the proxy logs, even if successful

Closes #1056
@rade rade merged commit b30de63 into weaveworks:master Jul 4, 2015
@rade rade deleted the proxy-stderr branch July 4, 2015 02:44
@rade rade added this to the current milestone Jul 4, 2015
@rade rade modified the milestones: current, 1.1.0 Jul 13, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants