What do you see as an issue?

The operator ExasolToS3Operator is missing a sample dag and documentation which would benefit users. In order to test the sample dag you need to have an Exasol account which requires a credit card (even with the free trial). If someone has an Exasol account and is willing to create a sample dag and test it, that would be a good bonus

Summary

As a consequence of one of my PRs, a bug was introduced into the master branch of the Argo Workflows codebase. This had instant repercussions (see Github Issue here) for new users that were consuming the tool. Whenever the docs provide a link to manifests, they point to the master branch (see [here](https://github.com/argoproj/ar

Description

Occasionally I get the following error when running sub-flows using create_flow_run and wait_for_flow_run

Task "wait_for_flow": Exception encountered during task execution!
Traceback (most recent call last):
  File "/root/miniconda3/lib/python3.8/site-packages/prefect/engine/task_runner.py", line 876, in get_task_run_state
    value = prefect.utilities.executor

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.

1. Make sure the include_sent_via_pipedream_flag prop is included in every send message action (not currently included in the "reply-to-a-message-thread" action).
2. Add a "Send as mrkdwn" optional prop to all Slack send message actions that use the `chat.postM

Is your feature request related to a problem? Please describe.

It's not especially common to generate a certificate file which includes its own CA chain as well. The common case would be to have a shared CA chain file for each node, and then each node gets its own certificate (which other nodes cannot access). The Java client, for example, already works like this. Right now, for inter-clust

NotebookRunner expects a string with Python code or a pathlib.Path object to a .py file. However, new users may do this:

NotebookRunner('script.py')

But instead they should do:

from pathlib import Path

NotebookRunner(Path('script.py'))

If passed a string, we should try to determine if the arguments "looks like a path to a file", and raise an err