You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I have modified the example and wanted to send the response of the calculator back on the bus, on a different topic. I would like to chain different functions to react on events down a chain. When I run "go run" process is stuck, nothing happens.
Happened upon this issue while evaluating the library for some work. Firing off new events from functions called from other events is something we'll need so I tried your example locally to see if I could get it to work.
Two changes are needed to make this work for me (macOS Sierra).
Use fmt.Sprintf on the arguments "calc1 calculated : %d\n", a+b. printer is only expecting a single parameter.
Use SubscribeAsync for the subscription to calc events. Transactional parameter can be either true or false.
@hanneslehmann Closing this issue. The problem is you have a subscribed synchronously therefore the callback has to complete first before the process can continue. The issue is the first call back never completes. @stackus 2nd suggestion is correct that you should SubscribeAsync if you want this behaviour.
Hi,
I have modified the example and wanted to send the response of the calculator back on the bus, on a different topic. I would like to chain different functions to react on events down a chain. When I run "go run" process is stuck, nothing happens.
Output
> go run poc3.go 1 calc1: 2 ^Csignal: interrupt
I am on linux 64 bit.
The text was updated successfully, but these errors were encountered: