Track task run count via Retry states #281
Merged
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
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.
Previously, the run count had to be provided manually by adding it to the run's context.
This PR modifies the
Retryingstate to carry arun_countattribute. When aTaskRunnerruns, the first thing it does is check if the initial task state is a Retrying state and, if so, if it indicates the last run number. If it does, the context is updated with one more than that value; otherwise, the context's run count is set to 1.Any time a Retry state is created, if no
run_countis provided it attempts to read it out of context. This way, user-generated Retry states (and signals) track the correct run count.