Skip to content
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

Bump pyqrack from 1.32.11 to 1.32.19 #2577

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 15, 2024

Bumps pyqrack from 1.32.11 to 1.32.19.

Release notes

Sourced from pyqrack's releases.

Option to disable low-fidelity exception

This release adds the option to disable the limiter exception on low QUnit fidelity estimate, by setting environment variable QRACK_DISABLE_QUNIT_FIDELITY_GUARD to any truthy value.

When QUnit encounters a situation where acting a coupler gate would require exceeding user-specified maximum system memory resources, it will automatically resort to replacing this gate with a "classical shadow" that will not require additional allocation. In the process, QUnit will decrease its internal first-principles unitary fidelity estimation under assumption that the classical shadow replacement effect is worst-case. If the fidelity estimate drops below floating-point rounding epsilon, QUnit will automatically throw to exit simulation early. However, particularly in cases of "anti-concentration," such as with universal random circuit sampling, this first-principles worst-case fidelity estimate might be very overly severe. In these cases, the worst-case fidelity estimate cannot necessarily be trusted not to be (potentially very) overly pessimistic, but the throw condition on low fidelity estimate can be disabled by assigning any value to environment variable QRACK_DISABLE_QUNIT_FIDELITY_GUARD.

Full Changelog: unitaryfund/qrack@vm6502qv9.12.23...vm6502q.v9.12.23 unitaryfund/pyqrack@v1.32.18...v1.32.19

sha1sum results: e65036260838ac596a5b0518a79b0f06926b28a3 pyqrack-1.32.19-py3-none-macosx_12_0_x86_64.whl f27a444f7376bb892724e212f3b1188aae2b3e50 pyqrack-1.32.19-py3-none-macosx_13_0_x86_64.whl fa4926eac7709a18a9b669a98486c16398b1124f pyqrack-1.32.19-py3-none-macosx_14_0_arm64.whl f69620de15afe3b6606c0287ce638d1f4c49e7d0 pyqrack-1.32.19-py3-none-macosx_15_0_arm64.whl 2cf24f10930d23e7e0dfc6ede852dd82a495fe63 pyqrack-1.32.19-py3-none-manylinux_2_31_x86_64.whl 3ebb349646fcf89cd89f12426689e74821ee4720 pyqrack-1.32.19-py3-none-manylinux_2_35_x86_64.whl 2f47136eb10bbf770e2ad3fb375a35bd10e6d8d3 pyqrack-1.32.19-py3-none-manylinux_2_39_x86_64.whl 3132be3673996d616ee6e1098d65b0cbc2fe93ee pyqrack-1.32.19-py3-none-win_amd64.whl 27d6fe47ad4d2c8aa7500b6599fea0a20b1f2b40 pyqrack-1.32.19.tar.gz fdfbcc678d0db2264fa819e6a1e1ab0d9b5c358b pyqrack_cpu-1.32.19-py3-none-macosx_12_0_x86_64.whl 50d4136af8ff288777c431e9b557c6844441730a pyqrack_cpu-1.32.19-py3-none-macosx_13_0_x86_64.whl 5bfd5565bf81e95dd0a55e1fe08d62ff4fd3ab02 pyqrack_cpu-1.32.19-py3-none-manylinux_2_31_x86_64.whl 3029d1e9089fc361bbd06963037111e354a4288b pyqrack_cpu-1.32.19-py3-none-manylinux_2_35_x86_64.whl 20ffa26950ae99218531908f0244fdc37b7b7bfa pyqrack_cpu-1.32.19-py3-none-manylinux_2_39_x86_64.whl 80666c6238801f9d9e5f02228dceaddcbb81ceac pyqrack_cpu-1.32.19-py3-none-win_amd64.whl 8a8312abe711fe6402aa3f3fd6ab6045cbd79421 pyqrack_cpu-1.32.19.tar.gz

Qrack errata commit bc1d5d8

Qrack errata commit bc1d5d89 🪨✌️💜

[Errata is not necessary; v1.32.17 is correct.]

Happy anniversary on 7 years of Qracking!

This release optimizes the QUnit classical shadows code and makes many various "micro-optimizations" largely around the goal of reducing division operations on literals and instituting a HALF_R1 macro.

The very first public Qrack repository commit (82744ec) was on December 20th, 2017. To personal memory, the first lines of the original Qrack code base were written (in GNU/Linux gedit, no less) in November, 2017, before "coming out of stealth" in December, a few weeks later. Dan remembers, he was excited by Microsoft's promotion of the first (preview) Q# SDK, which was released on December 11th of that year. It was actually through social media marketing channels about the first Q# SDK preview that he met Qrack coauthor @​bennbollay (via Dr. Nick Allgood). Benn basically taught Dan "Agile Methodology," through intensive pull request reviews, and he made invaluable contributions to early code standards, tooling, and even algorithms, particularly in QUnit, which he named.

We keep saying we're going to quit, one day... but we haven't, yet! For all these years, we've liked to try to take stock of the roadmap in November, annually, and give a "spit-shine" to any code standards that might have degraded in new implementation or changed due to finding better ways in the past year. Purely semantically, I take a look around at the code base, and I think we might not need a Qrack v10, yet, while the code standards look better than ever, to me!

I'm writing these commemorative release notes because Qrack got its annual November "spit-shine," this week. As many have heard me say in the past year or so, Qrack is a very "mature" project, maybe even "complete" at least in the implementation of the core library itself, besides integrations with third-party software, and so I want it in a perfectly honed form at any given moment I might "lovingly abandon" the core library as "complete." Yet, we've thought for at least a year, on-and-off, that the project might actually already be "complete," while we still manage to surprise ourselves week-to-week with new insights leading to new algorithms and optimizations.

Here's to 7 years of happy Qracking, and I wish the happiest of Fall and Winter holiday seasons to all who might read this! No immediate development priorities in the core Qrack library are on the immediate horizon, for now, again, but I wanted to make sure that Qrack was in absolute perfect condition for your holidays. Thank you! You rock!

Full Changelog: unitaryfund/qrack@vm6502qv9.12.18...vm6502qv9.12.23 unitaryfund/pyqrack@v1.32.16...v1.32.17

sha1sum results: 409141dcf699028cfd2cb631a8d7f2953e1f491b pyqrack-1.32.17-py3-none-macosx_12_0_x86_64.whl 165e1c987ad143148334df67868eeb333f257f31 pyqrack-1.32.17-py3-none-macosx_13_0_x86_64.whl

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [pyqrack](https://github.com/vm6502q/pyqrack) from 1.32.11 to 1.32.19.
- [Release notes](https://github.com/vm6502q/pyqrack/releases)
- [Commits](unitaryfund/pyqrack@v1.32.11...v1.32.19)

---
updated-dependencies:
- dependency-name: pyqrack
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the infrastructure For issues related to building, packaging, and continuous integration. label Nov 15, 2024
Copy link

codecov bot commented Nov 15, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.72%. Comparing base (9561b9f) to head (7d63fb6).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2577   +/-   ##
=======================================
  Coverage   98.72%   98.72%           
=======================================
  Files          92       92           
  Lines        4168     4168           
=======================================
  Hits         4115     4115           
  Misses         53       53           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure For issues related to building, packaging, and continuous integration.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants