Skip to content

client: log the tunneling startup exception instead of printing it to stdout - #1598

Open
bpalermo wants to merge 1 commit into
envoyproxy:mainfrom
bpalermo:up/stdout-log
Open

client: log the tunneling startup exception instead of printing it to stdout#1598
bpalermo wants to merge 1 commit into
envoyproxy:mainfrom
bpalermo:up/stdout-log

Conversation

@bpalermo

@bpalermo bpalermo commented Sep 7, 2026

Copy link
Copy Markdown

Description

This PR is related to #1605

When the encapsulating Envoy fails to start on the tunneling path, the exception was written to std::cout in addition to the logger. stdout is where nighthawk_client writes its formatted result, so consumers that parse it (for example --output-format json) could see a stray line in that error case. This logs it only.

Notes for Reviewers

One-line logging change on an error path; builds. Version history updated. Signed off per the DCO.

… stdout

When the encapsulating Envoy fails to start, the exception was written
to std::cout in addition to the logger. stdout is where nighthawk_client
writes its formatted result, so consumers that parse it (e.g. JSON) saw
a stray line in the error case. Log it only.

Signed-off-by: Bruno Palermo <[email protected]>
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.

1 participant