Description

Deprecate using global as the default region value in Google Dataproc operators and hooks. Make the default value None and then check if another value was passed. If not then raise a warning and set the value to global to preserve backward compatibility. Example of how it can be done:
https://github.com/apache/airflow/blob/805781b024fdcc8e93d695443b49d96747c085bf/airflo

Summary

Add --selector and other useful flags to argo {stop,terminate,resume,etc.}

Use Cases

You can list certain workflows with argo list --selector ..., you should be able to stop the same list of workflows

Message from the maintainers:

Impacted by this bug? Give it

Hello!

I've found an issue here:In order to deploy your flow to Kubernetes the flow is required to have a Docker Storage with the image pushed to a registry that your Kubernetes cluster has access to.

Page reference: https://docs.prefect.io/orchestration/tutorial/k8s.html

Is it in fact true that a flow deployed to Kubernetes EKS can't use s3 storage? If so, an explicit affirmation of th

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

From slack:

"Hi dagster team!
We are using dagster in our production pipeline. Our pipelines have different yaml files depending on the environment (e.g. staging, production). Currently we are facing a problem when changing our yaml files for the run config. It already happened some times that our yaml files aren’t valid, but we only discovered it when the pipeline was executed in production.

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