Skip to content

Start triggers in goroutine #166

@lixingwang

Description

@lixingwang

I'm submitting a ... (check one with "x")

[x] bug report => search github for a similar issue or PR before submitting
[] enhancement request
[] feature request
[] support request
[] general question

Current behavior (how does the issue manifest):
Today engine starts all trigger at main goroutine, main engine goroutine will be blocked if one of trigger fails to release the main engine goroutine.
Expected behavior:
All triggers should be independent so is that possible to start all trigger in different goroutine? otherwise, we need document the behavior to let user avoid block main goroutine.
Minimal steps to reproduce the problem (not required if feature enhancement):

What is the motivation / use case for changing the behavior?

Please tell us about your environment (Operating system, docker version, browser & verison if webui, etc):

Flogo version (CLI & contrib/lib. If unknown, leave empty or state unknown): 0.X.X

Additional information you deem important (e.g. issue happens only occasionally):

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions