Fixed empty error message if query parsing fails from unexpected exception. #574
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
j82w
added
bug
j82w
changed the title
j82w
changed the title
kirankumarkolli
approved these changes
Jul 19, 2019
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.
Pull Request Template
Description
If the incorrect service interop version is loaded it can cause unexpected exceptions which then has no serializedQueryExecutionInfo. This causes the user to get an error with no message information. If there is no message is now gives a warning to verify the version and gives the original exception content.
#573 will prevent this issue in the future.
#566 fixes the empty error message, but not the root problem
Type of change
Please delete options that are not relevant.