The Wayback Machine - https://web.archive.org/web/20201012003005/https://github.com/topics/workflow-engine
Skip to content
#

workflow-engine

Here are 275 public repositories matching this topic...

saig0
saig0 commented Sep 24, 2020

Describe the bug
A record can have a source record position. If the record is produced by the stream processing then it points to the record that was processed. Otherwise, the source record position is less than 0. This allows the see the causality.

Currently, there are some records that have a source record position but that are not produced by processing the record.

To Reproduce

samuell
samuell commented Aug 27, 2020

Analogous to how you can use basename to get only the filename of a path, like in:

p.SetOut("out1", "{i:in1|basename}.out.txt")

... it would be useful to also be able to extract only the directory, using dirname as a modifiers, so:

p.SetOut("out1", "{i:in1|dirname}/newfilename.txt")

This will also allow introducing another level of folders based on a previous

odin
ttymck
ttymck 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

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

You can’t perform that action at this time.
Morty Proxy This is a proxified and sanitized view of the page, visit original site.