Expose Prefect primitive runner task #10
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In the current implementation
QuantumRuntime.sampler, for example, calls a private method._setup_runnerto create a Prefect task to execute the Qiskit Primitives. This means the Prefect Task object is hidden from the end users, which was intention of this package to better align with the conventional Qiskit programming syntax.However, as a Prefect user, I also want to handle raw Task object to customize execution. This PR turns the task factory method into public so that experienced Prefect users can control more Prefect features.
The default tag of
primitive-executeis also dropped because tags depend on the design of flow.