This repository was archived by the owner on Jan 12, 2024. It is now read-only.
Fix to known QuantumProcessorTranslationException not being handled correctly #949
Conversation
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
swernli
approved these changes
Feb 19, 2022
swernli
pushed a commit
that referenced
this pull request
Feb 25, 2022
…orrectly (#949) * Add logging. * Add more logging. * Handle TargetInvocationException.
cgranade
pushed a commit
that referenced
this pull request
Feb 25, 2022
* Fix to known QuantumProcessorTranslationException not being handled correctly (#949) * Add logging. * Add more logging. * Handle TargetInvocationException. * Update wording for Azure submission errors * Fix error string in test case Co-authored-by: César Zaragoza Cortés <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 change fixes an issue in which known exceptions were not being handled correctly because they were wrapped inside a
TargetInvocationException.