workflow-engine
Here are 306 public repositories matching this topic...
Opened from the Prefect Public Slack Community
elliot: Hey folks is anyone else getting a deprecation warning on marshmallow? Something like:
...
/home/rof/.pyenv/versions/3.9.1/lib/python3.9/site-packages/marshmallow/fields.py:198
/home/rof/.pyenv/versions/3.9.1/lib/python3.9/site-packages/marshmallow/fields.py:198: RemovedInMarshmallow4Warning: Passing fi
-
Updated
Jun 15, 2021 - Java
-
Updated
Jun 16, 2021 - Elixir
-
Updated
Jun 9, 2021 - C#
-
Updated
Jun 8, 2021 - Python
-
Updated
Jun 16, 2021 - Go
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-
Updated
Jun 15, 2021 - Groovy
-
Updated
Jun 14, 2021 - Python
-
Updated
Apr 19, 2020 - Java
-
Updated
Jun 16, 2021 - Python
-
Updated
Feb 27, 2021 - Clojure
-
Updated
Jun 10, 2021 - Python
-
Updated
Jun 11, 2021 - JavaScript
-
Updated
Jun 16, 2021 - Python
This could be example that uses these supported syntax and APIs:
https://github.com/couler-proj/couler/tree/d34a690/couler/core/syntax
Group support
We should have a group support to handle permissions access from a LDAP, SSO, ...
allowed_resolvers_groups on templates for example.
admin_groups on configuration for example.
Describe the bug
Deploying a new job, then pulling logs via the CLI results in a panic (SIGSEGV).
To Reproduce
odin deploy -f test.job.yamlodin 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
-
Updated
Jun 14, 2021 - JavaScript
-
Updated
Apr 26, 2021 - Java
-
Updated
Mar 18, 2021 - Go
-
Updated
Apr 26, 2019 - PHP
-
Updated
May 31, 2021 - Python
-
Updated
Jun 16, 2021 - JavaScript
-
Updated
Dec 7, 2020 - C#
Improve this page
Add a description, image, and links to the workflow-engine topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the workflow-engine topic, visit your repo's landing page and select "manage topics."
Summary
From an archived workflow, click on "Resubmit" in the UI
The created workflow do not have the appropriate labels
/!\ the bug happens only for archived workflows (when you resubmit a "normal" workflow, the labels are kept)
Be cautious, some labels should not be copied (like workflows.argoproj.io or workflows.argoproj.io/phase)
however, the labels placed manually by the us