Description

When a command executed using KubernetesPodOperator fails, the alert email only says:
Exception: Pod Launching failed: Pod pod_name_xyz returned a failure
along with other parameters supplied to the operator but doesn't contain actual error message thrown by the command.

I am thinking similar to how xcom works with KubernetesPodOperator, if the command could write the err

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

Opened from the Prefect Public Slack Community

pat: This is a pretty minor problem as these things go, but it would be great if there was a way to disable the ASCII logo in Prefect Agent and Prefect Server, since it pollutes our server logs in DataDog. I can go hack the code, in Prefect, but it seems inelegant to have to re-apply such code after every version up

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

This is related to #647 - we already allow custom product paths, but it is not possible to customize product paths