The Wayback Machine - https://web.archive.org/web/20210504060332/https://github.com/topics/workflows
Skip to content
#

workflows

Here are 380 public repositories matching this topic...

longquanzheng
longquanzheng commented Feb 5, 2021

Is your feature request related to a problem? Please describe.
Need to search using LIKE operator with search attributes? eg, WorkflowType LIKE workflowType-prefix.*
Right now the workflowType is using keyword type for performance reason so it doesn't support wildcard search.

https://www.elastic.co/guide/en/elasticsearch/reference/current/keyword.html

keyword fields are untokeniz
appsmith
wfgydbu
wfgydbu commented Feb 5, 2021

SUMMARY

I just faced an embarrassed problem that command st2 action list keeps return 503.

I tried st2 --debug action list and the result in line HTTP_PROXY(uppercase) was empty. This mislead me that the proxy info was set(which is not).

I finally found that the root cause is a lowercase http_proxy env variable was set in the system.

So I think it maybe more friend

elsa-core
jwillmer
jwillmer commented Feb 25, 2021

As a power user I like to use existing webhook URLs in different workflows and be able to manage the endpoint centrally.

  • Option to define webhook URLs outside of a workflow under a specific name
  • Option to select the predefined webhook URL by name from a drop-down in the webhook activity

![image](https://user-images.githubusercontent.com/1503577/109169278-eca94400-777f-11eb-8b73-5ddbb006

onepanel

The open and extensible integrated development environment (IDE) for computer vision with built-in modules for model building, automated labeling, data processing, model training, hyperparameter tuning and workflow orchestration.

  • Updated Apr 29, 2021
  • Go
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
gh-action-pypi-publish
aiida-core
ramirezfranciscof
ramirezfranciscof commented Apr 26, 2021

Location: aiida.cmdline.utils.decorators

The method loads the DB environment only when it is necessary. We still need to test that it actually avoids doing it when it is not. An idea of how to do so from #4865:

we would have to mock the database loading env by a function that counts the number of times it is called with a global and raises the second time.

Improve this page

Add a description, image, and links to the workflows 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 workflows topic, visit your repo's landing page and select "manage topics."

Learn more