msgflo-setup fails with timeout error with noflo-runtime-msgflo

[bergie]

msgflo-setup does things in this order:

• Start participants, wait for STDOUT (Crash when connecting a client #92)
• Subscribe to fbp queue and wait for discovery messages

However, noflo-runtime-msgflo currently sends the discovery message only once, at start-up. This means msgflo-setup never receives it, as the fbp queue is subscribed only later.

[jonnor]

Yes, should subscribe right away, before starting the participants.