Alexey Rybalchenko

I have the same issue on Linux. It happens because wrangler was installed not by the same user that is executing it (is this intentional?). In my case i installed...

What I have in mind now, especially after considering possibility of having our own header and some other discussions we had, is to offer a new `fair::mq::Message` class. Which will...

What about other peers in this session, are they also stuck? Or only one process? This does not ring a bell, but I'll look into it. Do you have something...

> Can we simply get rid of the asynchronous API and the thread for the Region events? Does it serve any specific purpose? Yes, you can. If you do not...

yup.

> ok, but then this is not an option either, especially if we need to process at a few 100s Hz, no? Ideally you would handle all the required events...

FairMQ v1.4.45 contains changes that should significantly reduce the likelihood of this issue occurring. The mtx is locked fewer times and for a shorter period. A lockfree approach still under...

> Can you let me know about dynamically adding subchannels? Then I could do a REQ/REP to add/remove channels dynamically in my program? No, channels or sub-channels can only be...

I think to remove it completely we should at least have something equivalent in the SDK that would notify of the termination. Something on the controller side or in between...

It is trying to open a queue that should be created by the monitor. If it keeps doing it for you it likely means that the monitor is not (yet)...