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

When running the jupyter.jupyter.ExecuteNotebook task with output_format='html' the default settings for the HTMLExporter are used. There is no way to pass arguments to this exporter.

Proposed behavior

Allow passing arguments to the HTMLExporter.

Implementation suggestion

Something like html_exporter = nbconvert.HTMLExporter(**exporter_kwargs) on the

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.

Use Case

When you enter an invalid mode in dagster-graphql calls or the dagster CLI, we should tell you what modes would actually work instead, to help you debug.

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