workflow

Description

Currently, when submitting AWS Glue jobs using Airflow, we are seeing the below in the log :-
Polling for AWS Glue Job <job_name> current run state with status <job_run_state>. This request is to enhance this by providing more detailed information about the Glue Job, show the same continuous logs from Glue/Cloudwatch into the Airflow logs. This avoids airflow users having

PodPriority should be deprecated from workflow spec since Kubernetes uses PodPriorityClass to indicate the importance and priority of a pod relative to others.

https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/

https://github.com/argoproj/argo-workflows/blob/178bbbc31c594f9ded4b8a66b0beecbb16cfa949/pkg/apis/workflow/v1alpha1/workflow_types.go#L345-L346

Hello!

I've found an issue here:[Bitbucket Storage](https://docs.prefect.io/api/latest/storage.html#github) is a storage option that uploads flows to a Bitbucket repository as .py files.

Page reference: https://docs.prefect.io/orchestration/flow_config/storage.html#bitbucket

First, the link is incorrect. Second, should the line read more like Github where it references the repository

App: mautic
https://developer.mautic.org/

Triggers

• New Contact: Triggers when a new contact is created
• Updated Contact: Triggers when an existing contact is updated
• New Form Entry: Triggers when a form is submitted

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.

I added a small tutorial (triggered with python -m ploomber.onboard) but it doesn't have tests yet