Body

days_ago is deprecated apache/airflow#21653

We have several references to the function in test suite / example dags.

Task:
there should be no imports of airflow.utils.dates import days_ago in the code.
In most cases we can simple replace with datetime(2022, 1, 1)

Committer

• I acknowledge that I am a maintainer/committer of the Apache Airfl

Summary

The 2.x releases notes contains breaking changes: https://github.com/colinmarc/hdfs/releases/tag/v2.0.0

Message from the maintainers:

Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

Description

It looks like the installation command should be conda install -c conda-forge prefect python-kubernetes
https://github.com/PrefectHQ/prefect/blame/master/docs/orchestration/agents/kubernetes.md#L28

Logs:

(prefect) ubuntu@ip-172-31-7-79:~/perfect$ prefect agent kubernetes start --name "K8S Agent"
Traceback (most recent call

https://dagster.slack.com/archives/C01U954MEER/p1642163479382400:

Hi, I'm experiencing a bug when trying to write an ALS model from pyspark.ml.recommendation to S3 and reading it back in if this takes place within a dynamically executed graph (i.e. via dynamic mapping). I wrote a custom IO manager using the pattern f's3a://{self.s3_bucket}/{key}' as _uri_for_key similar to the one currently imp

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.

It looks like we're using v54.0 in the latest triggers but v20.0 in some of the actions (and test request), which Salesforce is deprecating soon.

Let's update so everything is on the latest version and consistent.

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