Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ui] add more detail in launch multiple runs' error text #26409

Merged
merged 1 commit into from
Dec 11, 2024

Conversation

dliu27
Copy link
Contributor

@dliu27 dliu27 commented Dec 11, 2024

Summary & Motivation

Previous error message was not clear to users when their "Launch all runs" operation fails due to ill-defined RunRequests. The feature requires RunRequests having job_name defined which is optional:

How I Tested These Changes

Tested locally

Copy link

Deploy preview for dagit-core-storybook ready!

✅ Preview
https://dagit-core-storybook-q1i6wj475-elementl.vercel.app
https://dliu27-manual-tick-dogfood.core-storybook.dagster-docs.io

Built with commit 3f9815c.
This pull request is being automatically deployed with vercel-action

@dliu27 dliu27 merged commit d59c5bf into master Dec 11, 2024
1 of 2 checks passed
@dliu27 dliu27 deleted the dliu27/manual-tick-dogfood branch December 11, 2024 17:20
pskinnerthyme pushed a commit to pskinnerthyme/dagster that referenced this pull request Dec 16, 2024
…26409)

## Summary & Motivation
Previous error message was not clear to users when their "Launch all
runs" operation fails due to ill-defined RunRequests. The feature
requires RunRequests having job_name defined which is optional:

https://github.com/dagster-io/dagster/blob/54b39a2595408ae723e77830919fc3219f268c70/python_modules/dagster/dagster/_core/definitions/run_request.py#L81

## How I Tested These Changes
Tested locally
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants