-
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
Fix BarrierBeforeFinalMeasurements
with loose bits
#8924
Fix BarrierBeforeFinalMeasurements
with loose bits
#8924
Conversation
We simply need to consider loose bits as well when constructing the new DAG layer. This isn't `DAGCircuit.copy_empty_like` because we don't want things like metadata and global phase.
Thank you for opening a new pull request. Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient. While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone. One or more of the the following people are requested to review this:
|
Pull Request Test Coverage Report for Build 3269945879
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, we basically had the same exact fix for DenseLayout
in #8843. I'm sure this isn't the last of the bugs we'll hit in old transpiler passes that don't get run regularly around loose bits.
@Mergifyio requeue |
✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically |
We simply need to consider loose bits as well when constructing the new DAG layer. This isn't `DAGCircuit.copy_empty_like` because we don't want things like metadata and global phase. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit 64c5eb6)
We simply need to consider loose bits as well when constructing the new DAG layer. This isn't `DAGCircuit.copy_empty_like` because we don't want things like metadata and global phase. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
We simply need to consider loose bits as well when constructing the new DAG layer. This isn't `DAGCircuit.copy_empty_like` because we don't want things like metadata and global phase. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit 64c5eb6) Co-authored-by: Jake Lishman <[email protected]> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Summary
We simply need to consider loose bits as well when constructing the new DAG layer. This isn't
DAGCircuit.copy_empty_like
because we don't want things like metadata and global phase.Details and comments
Fix #8923.