Skip to content
#

workflow-engine

Here are 353 public repositories matching this topic...

RowdyHowell
RowdyHowell commented Feb 28, 2022

Hello!

I've found an issue here:[Bitbucket Storage](https://docs.prefect.io/api/latest/storage.html#github) is a storage option that uploads flows to a Bitbucket repository as .py files.

Page reference: https://docs.prefect.io/orchestration/flow_config/storage.html#bitbucket

First, the link is incorrect. Second, should the line read more like Github where it references the repository

good first issue docs
samarabbas
samarabbas commented May 15, 2021

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

npepinpe
npepinpe commented Feb 15, 2022

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

kind/feature scope/broker good first issue scope/gateway
nooraangelva
nooraangelva commented Aug 4, 2021

Summary

What change needs making?
Example script on how to use created secret successfully.
I have tried myself using the following code from test
It creates a secret successfully but fails to echo the secrets value.

Use Cases

When would you use this?
when I n

enhancement good first issue help wanted

一款自带工作流引擎的Node.js全栈框架,一款面向开发者的低代码平台,更是一款兼具低代码的开箱即用和专业代码的灵活定制的PAAS平台。A Node.js full-stack framework with workflow engine, based on koa + egg + vue + framework7

  • Updated May 24, 2022
  • JavaScript
odin
tmkontra
tmkontra commented Aug 2, 2020

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
bug good first issue

Improve this page

Add a description, image, and links to the workflow-engine topic page so that developers can more easily learn about it.

Curate this topic

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."

Learn more