remove traceback for SSHException #2352
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While running a transport, if an
SSHExceptionis encountered, a full traceback is printed to the error log (viautil.tb_strings()). This is a less-than-ideal behavior, as we can't prevent this Python traceback from surfacing to the user (even when the actual error was handled gracefully). Looking at the rest of the codebase, it looks like the only other placesutil.tb_strings()is used is when catching a generic Exception (which makes sense, as this is by definition an unexpected failure and needs to be debugged). I propose removing the traceback log for SSHException.