Pipelines gets stuck if too many pipelines are in the same process

[flosell]

If too too many pipelines are in the same LambdaCD project/process, pipelines just get stuck in the middle of executing or just don't start at all:

Example to reproduce: https://gist.github.com/flosell/a8f0adf5f5fe1b3e61fb5c6adf6fbd93

[flosell]

The root problem seems to be the incorrect use of go-block to execute the children of either: Go-blocks assume that their body is non-blocking and therefore share a thread pool of availableProcessors * 2 + 42 threads. When starting too many pipelines with an either in front, this fills up the thread pool, leaving no room to process events or do any other work, therefore effectively stalling all of LambdaCD.

Solution:

• spawn normal threads in either
• remove use of blocking >!! from within go-blocks