-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[ui] Leverage ReexecutionStrategy for all “Re-execute” buttons except…
… step subset (#16731) ## Summary & Motivation This is a follow-up to #16728. I noticed this afternoon that we have some code paths in the UI which re-execute runs by passing a `ReexecutionStrategy` to the GraphQL mutation, and older code paths which generate the entire re-execution of the run from the base data (config YAML etc etc) themselves and pass it as execution metadata. Ironically the bug earlier today was that the latter was working and the former was not. To increase the chances that we catch bugs we want all re-executions to use the same machinery regardless of how they're started in the UI. This PR updates the Run Table and Run Details page to use ReexecutionStrategy for all callsites except two -- the "Selected Step" and "From Selected Step" options here. These two still assemble run execution variables manually. <img width="682" alt="image" src="https://github.com/dagster-io/dagster/assets/1037212/ecc2f2c3-c428-484b-8ef8-b0b4cfd98e83"> Nits: This PR also fixes two tiny issues: - The per-run actions dropdown goes from "Loading configuration" to "View configuration" which changes the width of the dropdown about 1s after it appears. This looks bad so I put a min-width on the menu item - The Actions button on the Runs Table was indented too much on the right side <img width="396" alt="image" src="https://github.com/dagster-io/dagster/assets/1037212/5847322b-16c1-4df5-b615-1b48ad196607"> ## How I Tested These Changes I re-executed a variety of runs from both the Runs table actions menu, Runs table per-run dropdown menu, and Runs detail page. Co-authored-by: bengotow <[email protected]>
- Loading branch information
Showing
8 changed files
with
80 additions
and
115 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
Oops, something went wrong.
47ad505
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deploy preview for dagit-core-storybook ready!
✅ Preview
https://dagit-core-storybook-192c05y68-elementl.vercel.app
Built with commit 47ad505.
This pull request is being automatically deployed with vercel-action