Skip to content
#

workflows

Here are 459 public repositories matching this topic...

appsmith
somangshu
somangshu commented Oct 19, 2021

Is there an existing issue for this?

  • I have searched the existing issues

Summary

Add an helper to state the usage of computed value property in table widget > column settings.

The helper should be:

  • The value computed & shown in each cell. Use {{currentRow}} to reference each row in the table. This property is not accessible outside the column settings.

Why shoul

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

yiminc
yiminc commented Jun 11, 2021

Is your feature request related to a problem? Please describe.
There is an optional config for namespace called "sampled retention days" that can be specified when create a namespace. It was created long ago as workaround for long retentions before long term archival was available.

Describe the solution you'd like
We should get rid of the sampled retention.

**Describe alternatives

elsa-core
sfmskywalker
sfmskywalker commented Jun 9, 2021

We currently have 3 workflow providers:

ProgrammaticWorkflowProvider: provides workflow blueprints based on the workflows coded with the fluent Workflow Builder API.
DatabaseWorkflowProvider: provides blueprints based on those stored in the database (JSON models stored by the designer).
StorageWorkflowProvider: provides blueprints based on JSON files stored on some hard drive or b

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
mbercx
mbercx commented May 10, 2021

Is your feature request related to a problem? Please describe

When I first wanted to obtain the entry point from a Group instance, I intuitively looked for the entry_point attribute. However, it seems that the entry point of a Group type can be obtained with the type_string attribute instead. Is there a difference between the type_string and the entry point? If not, perhaps we can

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