Apache Airflow version: 1.10.*
BackPort Packages version: 2020.10.5rc1

What happened:

BigQueryInsertJobOperator tries to start a BigQuery job by specifying a job_id which is a combination of dag_id, task_id, execution_date and an additional uniqueness_suffix.

https://github.com/apache/airflow/blob/master/airflow/providers/google/cloud/operators/bigquery.py#L2072

Summary

What happened/what you expected to happen?

After starting k3d cluster locally, if I run make start I get an error

➜  argo git:(learning) ✗ make start
# GIT_TAG=v2.10.0-rc1, GIT_BRANCH=learning, GIT_TREE_STATE=dirty, VERSION=latest, DEV_IMAGE=true, K3D=true
killall argo workflow-controller kubectl || true
No matching processes belonging to you were found
k3d start
Err

Created by Dylan Hughes via monday.com integration. 🎉

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

Problem to solve

The dagit CLI allows command options to be set via environment variables using the DAGIT prefix, implemented with Click's auto_envvar_prefix feature. I would like to be able to do the same with the dagster CLI.

Intended users

• DevOps Engineer

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