Summary

If a step group has pending/running nodes when it ends with an error node that failed to create a pod, the workflow cannot be retried because the completion states of pending/running nodes have not been synchronized, and they won't as the workflow itself finished with an error state.

My actual workflow failed with an API timeout of pod creation on a massive number of `withSequenc

Opened from the Prefect Public Slack Community

powp905: Hello,

We are currently looking at shelltask and dbtshelltask and we are wondering why helper_script is only in the constructor and why it cannot set when we call run. Th

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

Describe the bug
Deploying a new job, then pulling logs via the CLI results in a panic (SIGSEGV).

To Reproduce

1. odin deploy -f test.job.yaml
2. odin log -i {job_id}

vagrant@vagrant:~/odin$ odin log -i dea194794589
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0x79c764]

goroutine

This could be example that uses these supported syntax and APIs:

https://github.com/couler-proj/couler/tree/d34a690/couler/core/syntax

Helm chart with an optional development postgres DB included.

Currently the env variables injected are specific to this docker image https://github.com/barney-s/docker-airflow

Align it with https://github.com/puckel/docker-airflow and make necessary changes in the operator to make it work with both.

related to GoogleCloudPlatform/airflow-operator#10