Fix: Better Error Handling around the cipher manifest#954
Open
LuckyNoS7evin wants to merge 1 commit into
Open
Conversation
…iginal exception that caused YTE to use the cipher fallback code. This should give people better error handling and better logs for those errors
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
1 participant
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.
At the moment errors from the CipherManifest mean we don't get the original exception that caused YTE to use the cipher manifest fallback code.
This should give people better error handling and better logs for those errors
#902
N.B. This does not close the issue, but it does help with debugging and error handling around this issue