workflow-engine
Here are 351 public repositories matching this topic...
This issue is for developer to first contribute to dtm. It is for practice only, please just make changes to one file rather than all of them.
dtmsvr/trans_* files, add open source copyright comments, and send a PR for each file as a task
PR tutorial: https://opensource.com/article/19/7/create-pull-request-github
PR 中文教程: https://juejin.cn/post/6844903821521469448
-
Updated
Apr 19, 2022 - Elixir
Need to fix this TODO in the code:
// TODO: we need to consider adding execution time to mutable state
// For now execution time will be calculated based on start time and cron schedule/retry policy
// each time DescribeWorkflowExecution is called.
https://github.com/temporalio/temporal/blob/master/service/history/historyEngine.go#L1184
If you are using Conductor at the company you work with, add the name of your company and your Github handle to the list at https://github.com/netflix/conductor/blob/main/WHOSUSING.md
-
Updated
Apr 19, 2022 - Java
-
Updated
Mar 29, 2022 - C#
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
-
Updated
Apr 19, 2022 - Java
-
Updated
Apr 11, 2022 - Python
-
Updated
Apr 19, 2022 - Groovy
-
Updated
Feb 27, 2022 - Python
-
Updated
Apr 19, 2022 - Python
-
Updated
Apr 19, 2020 - Java
-
Updated
Mar 31, 2022 - Clojure
-
Updated
Oct 21, 2021 - Python
-
Updated
Apr 19, 2022 - JavaScript
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.
-
Updated
Apr 19, 2022 - Python
-
Updated
Apr 13, 2022
-
Updated
Apr 19, 2022 - JavaScript
-
Updated
Aug 13, 2021 - Go
-
Updated
Apr 19, 2022 - JavaScript
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
Apr 26, 2021 - Java
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
We could add a beacon endpoint that could by the UI to track usage of the UI
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