Clarify rzz out of range error message #2276
Merged
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
Some users reported that the "has been provided" wording sounded like the backend was providing that angle rather than it having been included in the circuit submitted by the user so here "provided" is changed to "requested" to make it more clear that it was the user's request that led to the error.
kt474
approved these changes
Jun 2, 2025
kt474
pushed a commit
that referenced
this pull request
Jun 4, 2025
Some users reported that the "has been provided" wording sounded like the backend was providing that angle rather than it having been included in the circuit submitted by the user so here "provided" is changed to "requested" to make it more clear that it was the user's request that led to the error.
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.
Some users reported that the "has been provided" wording sounded like the backend was providing that angle rather than it having been included in the circuit submitted by the user so here "provided" is changed to "requested" to make it more clear that it was the user's request that led to the error.