justinmclean opened a new issue, #4464: URL: https://github.com/apache/iggy/issues/4464
Split from #4452. ## Problem When a command fails, `main` returns the error (`core/cli/src/main.rs:359`), so Rust prints its `Debug` value. For example, `iggy ping` against a stopped server ends with: ``` Error: IggyClient(SdkError(CannotEstablishConnection)) ``` The top-level `Display` is only a label, for example "Iggy client error", so printing `Display` alone does not help either. ## Proposal Handle the error in `main`: print the error and its cause chain to stderr, one cause per line, and exit with code 1. Do not change the exit codes here. Distinct exit codes stay in #4452. ## Acceptance - `iggy ping` against a stopped server prints a readable message and its causes, with no Rust type names. - A failing command still exits with code 1. - Existing CLI integration tests that check error output are updated and pass. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
