-
Notifications
You must be signed in to change notification settings - Fork 16.6k
Remove API error from disabling submit#60473
Conversation
Prevent an API error from disabling the trigger dag form.
If you submitted once and then got an error. You had to close the modal and restart. You couldn't just change the erroring field. (ex: type an invalid custom run id, get an error, you can't submit even after editing the run id)
Ideally, we would have better error messages that we can map onto a specific field and only remove the disabling once that change was made. Maybe in the future.
Was generative AI tooling used to co-author this PR?
No
- Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
- For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
- When adding dependency, check compliance with the ASF 3rd Party License Policy.
- For significant user-facing changes create newsfragment:
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.
Backport failed to create: v3-1-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker fdd12cf v3-1-test
This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue
|
|
Manual backport #60658 |