You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the expected feature or enhancement?
Qiskit allows one to name registers pretty much anything because they are strings. However, the results of runtime are returned via attributes that do not accept all things a string does, e.g. not '0', ''?'`, etc. It would be nice to validate that register names are compatible with the Runtime service.
Acceptance criteria
The text was updated successfully, but these errors were encountered:
As a technical note to whoever picks this up, I imagine we want isidentifier to be true, and probably also iskeyword to be false, because the DataBin class allows access via attribute name.
I expect this fix should be made in qiskit, and ported here until 1.2. It's more a bug then an enhancement: coercion needs to fail for bad register names, because it will inevitably lead to invalid DataBins otherwise.
What is the expected feature or enhancement?
Qiskit allows one to name registers pretty much anything because they are strings. However, the results of runtime are returned via attributes that do not accept all things a string does, e.g. not
'0'
, ''?'`, etc. It would be nice to validate that register names are compatible with the Runtime service.Acceptance criteria
The text was updated successfully, but these errors were encountered: