Description
In the trigger page, there is a text area to enter (optional) conf json. It would be great if a sample JSON can be provided programatically while defining DAG

Use case / motivation

This will improve usability of the UI that triggers a DAG

Summary

If a step group has pending/running nodes when it ends with an error node that failed to create a pod, the workflow cannot be retried because the completion states of pending/running nodes have not been synchronized, and they won't as the workflow itself finished with an error state.

My actual workflow failed with an API timeout of pod creation on a massive number of `withSequenc

Current behavior

Slack, email and other notifications provide a standardized text and backend info.

Proposed behavior

Users can add custom texts to the notifications.

Example

Prefect
Failed
awesome-flow is now in a Failed state
Message
Some reference tasks failed.
Prefect notification
@colleague, please analyze possible root causes.

Ideas for Imp

Use case

Polyaxon tracking can be used to automatically log all information generated by Ludwig.

We should probably think about adding support for Polyaxon's tracking module in Ludwig contrib.

Summary

It's not obvious that users can tag solids and pipelines. We should at least update this example to mention solid level tags or include a solid tag example

Reproduction

Dagit UI/UX Issue Screenshots

Additional Info about You

Issue

16 files has some sort of Sugar Pro references in code as comments.
Those should be removed

Steps to Reproduce

Try the search with BEGIN: pro
https://github.com/salesagility/SuiteCRM/search?q

Had the branch ancestry:

branch-1
  branch-2-bug-fix
    branch-3

All three branches had an open PR. branch-2-bug-fix‘s PR was a duplicate of a fix that someone else had already put in and merged at the same time. I closed the PR on branch-2-bug-fix and ran git town kill on that branch.

I was expecting it to change the base branch of branch-3‘s PR but instead it closed it