Apache Airflow Provider(s)

google

Versions of Apache Airflow Providers

apache-airflow-providers-google==6.3.0

Apache Airflow version

2.1.4

Operating System

macOS Big Sur version 11.6.1

Deployment

Composer

Deployment details

No response

What happened

Postgres JSON column output contains extra \:

`{"info": "{"phones": [{"type": "mobile", "phone\

Summary

We could add a beacon endpoint that could by the UI to track usage of the UI

<TrackEvent event='viewNodeSummary'/>

This just makes a HTTP request to /api/v1/collect?t=trackEvent&event=viewNodeSummary, similar to:

https://developers.google.com/analytics/devguides/collection/protocol/v1/reference

This event could be logged, with the SSO subject/email so Splunk

Current behavior

wait_for_flow_run currently times out after 12 hours. This value is hardcoded in watch_flow_run here.

so for subflows greater than 12 hours, this task will exit unexpectedly

Proposed behavior

Make it configurable by passing a value of

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.

Let's put this under helper_functions for now.

This action should just take any type of input and simply export the value, so users don't have to write custom code to define variables they need to reference.

For example:

export default defineComponent({
  props: {
    config: {
      type: "object",
      label: "Configuration",
      description: "Enter key-value pairs that you

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

User executes this:

ploomber task some-task

Print something like this:

'some-task' executed successfully!

Products:
  products/report.html
  products/data.csv