workflow

Description

Snowflake client drivers perform OCSP checking by default when connecting to a service endpoint. In normal circumstances, we should never turn off OCSP checking, and keep the default security posture of OCSP checking always ON. Only in rare emergency situations when Airflow is unable to connect to Snowflake due to OCSP issues should we consider using this workaround temporarily

It should be 0/1 when pending/running and 1/1 when complete.

Description

It is not an actual bug but in the documentation here -> https://docs.prefect.io/orchestration/concepts/api.html#queries
flow_run actually needs to be flow_runs.
Otherwise it does not work for me.

Expected Behavior

Documentation should be updated.

Reproduction

Summary

"This is pretty confusing: are the types here config types? the types of the resource? if the former, they don't seem right; if the latter, it's not helpful to have Any for essentially any meaningful resource -- we should either allow the user to give us a hint of what type the resource is, or cut this f

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.

Description

When using the zbctl to create a worker we are able to set some flags, like the timeout of the job activation, but it is not clear from the help what the unit is and how the parameter should look like.

[zell camunda-cloud/ ns:bece6b37-3b9c-4fd0-8e79-4990cd0d057d-zeebe]$ zbctl create worker
Error: accepts 1 arg(s), received 0
Usage:
  zbctl create worker <type> [flag

I'm trying to replace the background diagram-maker canvas svg, with custom small circular nodes. So, probably this lead to more than 5000 number of circular nodes.

This is causing Performance Issues. Any suggestions, how to optimize this usecase?