[ https://issues.apache.org/jira/browse/PROTON-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304032#comment-14304032 ]
ASF subversion and git services commented on PROTON-757: -------------------------------------------------------- Commit 78e54ee7d108dc3e37c663afdecde18525f6b1cd in qpid-proton's branch refs/heads/master from [~dnwe] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=78e54ee ] PROTON-757: stop transport errs printing to stderr This looks to be since e5696c19 - pn_do_error already sets the transport->condition fields which are accessible as a pn_error from pn_transport_error, so we shouldn't really output them to stderr unless tracing is enabled. > [PATCH] proton-c: transport errors are output to stderr in 0.8 onwards > ---------------------------------------------------------------------- > > Key: PROTON-757 > URL: https://issues.apache.org/jira/browse/PROTON-757 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c > Affects Versions: 0.8 > Reporter: Dominic Evans > Assignee: Dominic Evans > Attachments: > 0001-Don-t-trace-transport-errors-unless-PN_TRACE-set.patch > > > This looks to be since e5696c19. > pn_do_error already sets the transport->condition fields which are accessible > as a pn_error from pn_transport_error, so we shouldn't really output them to > stderr unless tracing is enabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)