Decode key_type in error message strings.#55
Merged
ojarva merged 4 commits intoojarva:masterfrom May 16, 2019
Merged
Conversation
Owner
|
Ah well, there is a new pylint that will complain about old code, causing tests to fail. I won't have time to fix those issues today. As your second undoes part of what you did on the first commit, please squash the commits into one. |
This avoids strings like b'ssh-rsa' in the error messages.
benkonrath
force-pushed
the
decode-key-type-in-errors
branch
from
30e9f8b to
3fe6182
Compare
Contributor
Author
|
No problem. I've just squashed the two commits into one. |
This file contains hidden or 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
2 participants
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.
This avoids strings like b'ssh-rsa' in the error messages. I didn't add tests because I wasn't sure what you'd want to do for this - if anything. Thanks for your work on this library.