Add built-in list of wait keys to pipeline #278
Draft
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
ljgray
changed the title
ljgray
force-pushed
the
ljg/pipeline-after
branch
from
131bdaf
to
68d7b07
Compare
ljgray
force-pushed
the
ljg/pipeline-after
branch
from
68d7b07
to
e180a00
Compare
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.
Implements a list of keys used to control task run order. Keys provided to a task in the
waitqueue tell the task that those keys must have been generated before the task can be run, even if those keys are not actually required by the task in isolation.The
single_waitargument is used to control whetherwaitkeys must only be generated once or if they must be re-generated each time the task wants to callnext.