Description

As the Airflow 2.0 is coming nearer it would be awesome to refresh the Airflow WebUI. By this it mostly means:

• using some "modern colors" (how about Airflow logo palette?)
• fixing some padding/spacing
• and other small HTML / CSS touches

Use case / motivation

The main point is to refresh the look, not to rewrite the Web UI.

Related Issues

Apach

Summary

What happened/what you expected to happen?

When requesting for logs using API server, the timestamp is always prepended to the actual output generated by the main process inside container. The logOptions.timestamps has no effect at all. The main process inside container does not log timestamps in my example.

I took a look at the source code, there could be an issue with [thi

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