Body

The goal is to refactor the code so that we can remove this TODO
https://github.com/apache/airflow/blob/7640ba4e8ee239d6e2bbf950d53d624b9df93059/airflow/providers/amazon/aws/hooks/emr_containers.py#L174-L176

More information about the concerns can be found on apache/airflow#16766 (comment)

Committer

• I acknowledge that I am a maintainer/

Summary

It is possible to access individual parameters, labels, or annotations from within a workflow via

• workflow.parameters.<NAME>,
• workflow.labels.<NAME>,
• and workflow.annotations.<NAME> respectively.

It is also possible to get all parameters as a JSON string:

• workflow.parameters

It would be great if also labels and annotations could be exposed that way:

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?