-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change DAGCircuit::collect_runs()
return to not be an Option
#13109
Comments
Hi, while I'm working on another issue I would love to work on this one as well. If it's ok to assign a second issue to me, kindly do so. Thanks |
@tonmoy-b assigned, thanks! |
i have created a pull request for this issue. please let me know if formatting is correct and perhaps how to test better - this is my first qiskit issue and not too familiar with rust. |
Hi Cameron, someone will review your PR code but I think you need to sign the CLA first. I'm not sure how to transfer the assignee tag to you but maybe that can be done later. You probably should sign the CLA for now. |
i just signed it - thank you for the heads up. |
any suggestion on my pull request? happy for feedback. |
is it okay that some of the workflows are failing? |
Make sure you run tox, tox -eblack and tox -elint in your local system before you push. The last in particular will give you code formatting errors that you should correct so there's no issues later on |
I need till this weekend or Monday, I'll get back to you then but maybe one of the project maintainers will give a review before that. |
do you know how long it may take for pull request to be approved or to get feedback? it has just passed all the tests. @tonmoy-b @AngeloDanducci |
Originally posted by @kevinhartman in #13013 (comment)
To fix this issue we should update the
collect_runs()
method incrates/circuit/src/dag_circuit.rs
to internally unwrap the return from rustworkx and not return an option.The text was updated successfully, but these errors were encountered: