Bug/607 fidelity statevector kernel cannot be pickled (backport #778) #782
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
* Made fidelity_statevector_kernel picklable Added a new param to store cache size and a custom __getstate__ and __setstate__ to handle removing and re-initliasing the lru cache during pickle/unpickling respectively. * updated notes * name changes * spell corrections * Updated description * Added unittest for pickling * Spelling changes * Making error messages clearer * Spelling -_- * Update releasenotes/notes/fix-fid_statevector_kernel-pickling-b7fa2b13a15ec9c6.yaml Co-authored-by: Declan Millar <declan.millar@ibm.com> * Update .gitignore Co-authored-by: Declan Millar <declan.millar@ibm.com> * Update test/kernels/test_fidelity_statevector_kernel.py Co-authored-by: Declan Millar <declan.millar@ibm.com> * Update qiskit_machine_learning/kernels/fidelity_statevector_kernel.py Co-authored-by: Declan Millar <declan.millar@ibm.com> * Update test/kernels/test_fidelity_statevector_kernel.py Co-authored-by: Declan Millar <declan.millar@ibm.com> * Update qiskit_machine_learning/kernels/fidelity_statevector_kernel.py Co-authored-by: Declan Millar <declan.millar@ibm.com> * Added Any class --------- Co-authored-by: M. Emre Sahin <40424147+OkuyanBoga@users.noreply.github.com> Co-authored-by: Declan Millar <declan.millar@ibm.com> Co-authored-by: Anton Dekusar <62334182+adekusar-drl@users.noreply.github.com> (cherry picked from commit c59063a)
mergify
bot
requested review from
woodsp-ibm,
adekusar-drl,
smens,
edoaltamura,
oscar-wallis,
OkuyanBoga and
Benjamin-Symons
as code owners
Pull Request Test Coverage Report for Build 8099320004Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
edoaltamura
approved these changes
Feb 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automatic backport of pull request #778 done by Mergify.
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com