Fix handling of multiple level exceptions in message header #255
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
kived
force-pushed
the
fix-exception-handling
branch
from
9b6dfb7
to
e6fb0bc
Compare
|
Thanks! |
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.
Fixes #197. The serialized exception appears only once, after the list of class/message pairs.
Also changes the generated Python exception message to be more readable.
Previous:
pyorient.exceptions.PyOrientCommandException: com.orientechnologies.orient.core.exception.OValidationExceptionjava.lang.NumberFormatException - impossible to convert value of field "coordinates"For input string: "UNKNOWN"New:
pyorient.exceptions.PyOrientCommandException: com.orientechnologies.orient.core.exception.OValidationException - impossible to convert value of field "coordinates", java.lang.NumberFormatException: For input string: "UNKNOWN"