Skip to content

Avoid using rustworkx 0.16.0 methods in vf2_utils (backport #14513) #14534

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

Merged
merged 2 commits into from
Jun 12, 2025

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jun 4, 2025

Summary

In #14218 the vf2_utils module was updated to use the PyDiGraph.neighbors_undirected() method which was added in 0.16.0. However that PR neglected to bump the minimum required version of rustworkx to 0.16.0 from 0.15.0 which is the current minim version listed. While we could bump the minimum version (see #14507) to rustworkx 0.16.0 using this method isn't strictly necessary and #14218 was backported to stable branches and backporting a version bump is not desireable. This commit instead just updates the rustworkx usage to use APIs in 0.15.0.

This PR will need to be backported to stable/1.4 and stable/2.0 to fix compatibility with the listed rustworkx requirement. However, in the backport a fix note will be needed to document that the release fixes compatibility with the listed requirement.

Details and comments
This is an automatic backport of pull request #14513 done by Mergify.

* Avoid using rustworkx 0.16.0 methods in vf2_utils

In #14218 the vf2_utils module was updated to use the
`PyDiGraph.neighbors_undirected()` method which was added in 0.16.0.
However that PR neglected to bump the minimum required version of
rustworkx to 0.16.0 from 0.15.0 which is the current minim version
listed. While we could bump the minimum version (see #14507) to
rustworkx 0.16.0 using this method isn't strictly necessary and #14218
was backported to stable branches and backporting a version bump is not
desireable. This commit instead just updates the rustworkx usage to use
APIs in 0.15.0.

This PR will need to be backported to stable/1.4 and stable/2.0 to fix
compatibility with the listed rustworkx requirement. However, in the
backport a fix note will be needed to document that the release fixes
compatibility with the listed requirement.

* Correctly handle duplicates across successors and predecessors

(cherry picked from commit 9aa1a29)
@mergify mergify bot requested a review from a team as a code owner June 4, 2025 15:43
@qiskit-bot
Copy link
Collaborator

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 following people are relevant to this code:

  • @Qiskit/terra-core

@github-actions github-actions bot added the Changelog: None Do not include in changelog label Jun 4, 2025
@github-actions github-actions bot added this to the 1.4.4 milestone Jun 4, 2025
@coveralls
Copy link

coveralls commented Jun 4, 2025

Pull Request Test Coverage Report for Build 15490517459

Details

  • 3 of 3 (100.0%) changed or added relevant lines in 1 file are covered.
  • 29 unchanged lines in 3 files lost coverage.
  • Overall coverage decreased (-0.03%) to 88.113%

Files with Coverage Reduction New Missed Lines %
crates/qasm2/src/expr.rs 1 94.23%
crates/qasm2/src/lex.rs 4 92.48%
crates/qasm2/src/parse.rs 24 96.22%
Totals Coverage Status
Change from base Build 15331629193: -0.03%
Covered Lines: 72933
Relevant Lines: 82772

💛 - Coveralls

@mtreinish mtreinish modified the milestones: 1.4.4, 2.0.2, 2.0.3 Jun 4, 2025
@mtreinish mtreinish added Changelog: Bugfix Include in the "Fixed" section of the changelog and removed Changelog: None Do not include in changelog labels Jun 4, 2025
@Cryoris Cryoris added this pull request to the merge queue Jun 12, 2025
Merged via the queue into stable/2.0 with commit d2ee4ba Jun 12, 2025
26 checks passed
@Cryoris Cryoris deleted the mergify/bp/stable/2.0/pr-14513 branch June 12, 2025 12:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Changelog: Bugfix Include in the "Fixed" section of the changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants