raise DagsterError for trying to re-execute a not failed run #17535
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
|
Current dependencies on/for this PR: This stack of pull requests is managed by Graphite. |
prha
approved these changes
Oct 31, 2023
alangenfeld
force-pushed
the
al/10-31-raise_DagsterError_for_trying_to_re-execute_a_not_failed_run
branch
from
a3cd3fc to
5ad4a1e
Compare
alangenfeld
deleted the
al/10-31-raise_DagsterError_for_trying_to_re-execute_a_not_failed_run
branch
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.
To ensure the message is visible in environments where
checkexceptions are not default shown (like cloud)How I Tested These Changes
existing test coverage