- 20 Nov, 2017 1 commit
-
-
Luca Boccassi authored
Solution: build all the objects separately before the link step, to avoid rebuilding when doing both static and shared builds
-
- 19 Nov, 2017 1 commit
-
-
Luca Boccassi authored
Solution: don't redefine preprocessor macro if it's already defined in platform.hpp
-
- 16 Nov, 2017 1 commit
-
-
Luca Boccassi authored
Solution: set 0 linger on the sockets immediately after creating them rather than immediately before closing them. Running through helgrind/drd highlights a few race conditions, one of which is the setting of linger vs checking it when closing the socket. Work around it by setting it immediately to fix the test hangs.
-
- 10 Nov, 2017 1 commit
-
-
Luca Boccassi authored
Solution: bind to wildcard and let the OS pick a free port instead of using an hard-coded 12345 TCP port
-
- 08 Nov, 2017 1 commit
-
-
Rolf Timmermans authored
Problem: REQ socket with ZMQ_REQ_RELAXED does not report ZMQ_POLLOUT when queried for events after first message. Solution: Check for strictness before returning false if no reply has been received.
-
- 25 Oct, 2017 1 commit
-
-
f18m authored
Change ZMQ_THREAD_AFFINITY to ZMQ_THREAD_AFFINITY_CPU_ADD/ZMQ_THREAD_AFFINITY_CPU_REMOVE. Avoid prefix thread names when no prefix was set.
-
- 17 Oct, 2017 3 commits
-
-
Luca Boccassi authored
Solution: define __STDC_LIMIT_MACROS in test_timers.cpp before including testutil.hpp so that the definitions are included
-
Luca Boccassi authored
Solution: print unsigned integers instead of size_t to avoid the error: error: ISO C++ does not support the 'z' gnu_printf length modifier due to very old version of GCC.
-
f18m authored
* Add ZMQ_THREAD_NAME_PREFIX ctx option
-
- 16 Oct, 2017 2 commits
-
-
Luca Boccassi authored
Solution: this will break once the tested APIs move from DRAFT to STABLE so instead check for the specific macros.
-
f18m authored
* Background thread scheduling - add ZMQ_THREAD_AFFINITY ctx option; set all thread scheduling options from the context of the secondary thread instead of using the main process thread context! - change ZMQ_THREAD_PRIORITY to support setting NICE of the background thread when using SCHED_OTHER
-
- 09 Oct, 2017 1 commit
-
-
Luca Boccassi authored
Solution: add ZMQ_ZAP_ENFORCE_DOMAIN to hide backward incompatible change and make it disabled by default. In a future release that breaks API compatibility we can then switch the default to enabled in order to achieve full RFC compatibility. Fixes #2762
-
- 06 Oct, 2017 2 commits
-
-
Luca Boccassi authored
Solution: pre-create the second socket to save a few cycles between closing the old one and binding the new one
-
Luca Boccassi authored
Solution: name it after the test to avoid possible clashes when running tests in parallel.
-
- 05 Oct, 2017 1 commit
-
-
Ilya Kulakov authored
Solution: Don't unlink file on close File may not belong to the socket at that point.
-
- 19 Sep, 2017 6 commits
-
-
sigiesec authored
Solution: replaced by "routing id"
-
sigiesec authored
Solution: use "routing_id" instead
-
sigiesec authored
Solution: renamed routing_id fields in pipe_t, renamed ZMQ_CONNECT_RID to ZMQ_CONNECT_ROUTING_ID
-
sigiesec authored
Solution: replace by "routing id"
-
Luca Boccassi authored
Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
-
sigiesec authored
receive an ERROR (probably because the connection is closed before) Solution: wait for client-side monitor events before closing the client socket Fixes #2705
-
- 18 Sep, 2017 5 commits
-
-
sigiesec authored
Solution: added tests
-
sigiesec authored
mechanisms Solution: uniformly require a ZAP domain to be set to activate ZAP handling, clarify comment on Stonehouse pattern
-
sigiesec authored
Solution: added test & some improvements of test utils
-
sigiesec authored
Solution: emit events as expected by tests, and refuse connections when ZAP is required but no handler started Addresses #2711 partially
-
sigiesec authored
Solution: added test case for NULL/PLAIN/CURVE
-
- 07 Sep, 2017 2 commits
-
-
Doron Somech authored
-
sigiesec authored
Solution: renamed routing_id fields in pipe_t, renamed ZMQ_CONNECT_RID to ZMQ_CONNECT_ROUTING_ID
-
- 06 Sep, 2017 2 commits
-
-
sigiesec authored
Solution: replace by "routing id"
-
Luca Boccassi authored
Solution: split each stat into its own frame, to make it simpler and easier to use it, especially from high level bindings
-
- 05 Sep, 2017 3 commits
-
-
Luca Boccassi authored
Solution: ifdef it until it's declared stable
-
Luca Boccassi authored
Solution: trucate 64 bit stats in test_proxy, as it's much easier than to try and print 64 unsigned integers in a portable way
-
f18m authored
* Issue #2736: Add STATISTICS command to zmq_proxy_steerable()
-
- 01 Sep, 2017 7 commits
-
-
Luca Boccassi authored
Solution: don't pass it
-
sigiesec authored
Solution: added tests
-
sigiesec authored
Solution: use inproc transport instead
-
sigiesec authored
Solution: refactoring
-
sigiesec authored
Solution: modify order of operations, add diagnostic output
-
sigiesec authored
Solution: added call
-
sigiesec authored
Solution: added test case (with dummy implementation of zmq_socket_get_peer_state)
-