This issue is part of #8765

Rule

Create CustomExecutorsRequireFullPathRule which corresponds to

Custom executors is loaded using full import path

entry in UPDATING.md. This rule should allow users to check if their current configuration needs any adjusting
before migration to Airflow 2.0.

How to guide

To implement a new rule, create a class that inherits from `airflow.upgrade.rules.b

Summary

The documentation around retry loops explains that it is possible to specify both the duration and the maxDuration as "durations", specifically

e.g.: "2m", "6h", "1d"

However, specifying the duration as "1d" leads to an error: "unable to parse 1d as a duration". In any case, a full accounting of the allowed duration specifications in the docs would be much appreciated.

Description

I just run MySQLFetch task:

mysql = MySQLFetch(
        host="...",
        port=3306,
        db_name="...",
        user="...",
        password="...",
        query="SELECT * FROM ... LIMIT 1"
    )
mysql.run()

And I get this:

Traceback (most recent call last):
  File "/Users/danielnuriyev/simplisafe/scripts/lib/python3.8/site-packages/IPython/core/int

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.

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

User facing errors about invalid values for the DAGSTER_HOME environment variable are not helpful, and sometimes reference internal functions. These error messages should be updated to explain to the user what DAGSTER_HOME is and how to set it.

When DAGSTER_HOME is not set:

raise DagsterInvariantViolationError(
dagster.core.errors.DagsterInvariantViolationError: DAGSTER_HOME 

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