Open nonhermitian opened 3 days ago
After talking to the internal team, this should actually raise an exception across all circuit functions during the input validation phase
Why is that? It is a valid circuit, and is useful for testing; it basically verifies if a circuit function can cleanup spam errors.
This is probably fixed in the same manner as #27 where it is an incompatibility with the standard pubs specification
Steps to reproduce the problem
What is the current behavior?
Gives
{'error': 'An unexpected error occurred. Please try again later. If the issue persists, please contact support.'}
What is the expected behavior?
Should work like it does on other circuit functions