Description

I am using Airflow to move data periodically to our datalake and noticed that the MySQLToS3Operator has tempalted fields and the DynamoDBToS3Operator doesn't. I found a semi awkward workaround but thought templated fields would be nice.
I supposed an implementation could be as simple as adding

template_fields = (
's3_bucket',
's3_key',
)

to the Operator

Both successful workflows and stopped workflows are generating similar kind of events with 'reason' as 'WorkflowSucceeded'. There is no way to differentiate successful vs stopped events to trigger different down streams based on the status.

What change needs making?
Would like to see reason as 'workflowStopped' for stopped workflows.

Use Cases

We are using [Argo events](https://argoproj

Current behavior

You get an error if you try to upload the same file name

azure.core.exceptions.ResourceExistsError: The specified blob already exists.
RequestId:5bef0cf1-b01e-002e-6

Proposed behavior

The task should take in an overwrite argument and pass it to [this line](https://github.com/PrefectHQ/prefect/blob/6cd24b023411980842fa77e6c0ca2ced47eeb83e/src/prefect/

Summary

In dagster/js_modules/dagit/packages/core/src/pipelines/SidebarOpContainer.tsx there is an error message "Could not load solids". We should rewrite for an op/SDA world.

Reproduction

Dagit UI/UX Issue Screenshots

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.

Hey everyone, I hope y'all enjoyed your holidays.
I want to create SuiteCRM users via the V8 api, but the response is invalid json and contains some generic validation error message.

I'm not sure whether my request is actually malformed or the error message just shouldn't appear.

Actions

• Create an Item | Creates an item
• Update Item Name | Update an item's name
• Create a Board | Creates a new board
• Create a Group | Creates a new group in a specific board
• Create an Update | Creates a new update

Describe the bug

The attached BPMN model produces a deployment error without saying what the real issue is.

zbctl output

Error: rpc error: code = InvalidArgument desc = Command 'CREATE' rejected with code 'INVALID_ARGUMENT': Expected to deploy new resources, but encountered the following errors:
'2 - Vacation Request Part