- 27 May, 2015 14 commits
-
-
Lucas Russo authored
-
Lucas Russo authored
-
Lucas Russo authored
-
Lucas Russo authored
This is unnecessary, as even if we force the user to input a valid range, nothing guarantees that the specified board will be plugged in the crate.
-
Lucas Russo authored
-
Lucas Russo authored
These macros were probably copied over without checking, resulting in this set of duplicate MACROS.
-
Lucas Russo authored
-
Lucas Russo authored
-
Lucas Russo authored
This was done as devio_loop () is more semantic and widespread.
-
Lucas Russo authored
Our actors/pipes were not terminating properly due to asynchronous behaviour of actors/pipes. Now, a proper handshake accurs between DEVIO and actor/pipes SMIOs and they terminate gracefully.
-
Lucas Russo authored
-
Lucas Russo authored
Our actors/pipes were not terminating properly due to asynchronous behaviour of actors/pipes. Now, a proper handshake accurs between DEVIO and actor/pipes SMIOs and they terminate gracefully.
-
Lucas Russo authored
There was a mismatch between the enum declaration and the error description structure, causing the error to print an unexpected message.
-
Lucas Russo authored
-
- 26 May, 2015 1 commit
-
-
Lucas Russo authored
-
- 22 May, 2015 6 commits
-
-
tcp://127.0.0.1:9999Lucas Russo authored
With the previous tcp//*:9999, clients could not connect to the broker. Needs further investigation.
-
Lucas Russo authored
-
Lucas Russo authored
We were treating mlm_client_t * as an zactor_t * or sock_t *, which is clearly wrong. Now, we first get the actor reference from mlm_client_t * and then resolve the actor to the libzmq socket.
-
Lucas Russo authored
The regular PIPE socket (pipe_mgmt) created on zactor_new () will be used for string commands and the pipe_msg wil be used for general messages.
-
Lucas Russo authored
-
Lucas Russo authored
-
- 21 May, 2015 10 commits
-
-
Lucas Russo authored
With the new CZMQ 3.0.0 we no longer store a libzmq socket type (void *), but a zactor_t polymorphic type. Now, in order to get access to the libzmq socket reference we need to call zsock_resolve ().
-
Lucas Russo authored
-
Lucas Russo authored
With the new CZMQ 3.0.0 we no longer store a libzmq socket type (void *), but a zactor_t polymorphic type. Now, in order to get access to the libzmq socket reference we need to call zsock_resolve ().
-
Lucas Russo authored
-
Lucas Russo authored
-
Lucas Russo authored
-
Lucas Russo authored
This is not needed anymore as the log directory must be mounted before our software initializes
-
Lucas Russo authored
This uses makeself script available at "https://github.com/megastep/makeself"
-
Lucas Russo authored
-
Lucas Russo authored
-
- 20 May, 2015 9 commits
-
-
Lucas Russo authored
-
Lucas Russo authored
With this, we generate the lib dependencies as soon as possible and not have the linker warn us later on, on dev_mngr or dev_io linking.
-
Lucas Russo authored
If available UUID will generate more sensible UUIDs. If not, CZMQ is going to use /dev/random
-
Lucas Russo authored
-
Lucas Russo authored
-
Lucas Russo authored
-
Lucas Russo authored
-
Lucas Russo authored
Now we use the Malamute broker instead of Majordomo
-
Lucas Russo authored
The hardcoded filename is not robust and should change in the near future
-