- 04 Apr, 2017 1 commit
-
-
bjovke authored
Unnecessary dynamic memory allocation for zmq::socket_poller_t in zmq_poller_poll(). Fixed by allocating zmq::socket_poller_t from stack.
-
- 27 Mar, 2017 1 commit
-
-
Thomas Braun authored
Solution: Pass (std::nothrow) as done in all other places.
-
- 26 Mar, 2017 1 commit
-
-
evoskuil authored
-
- 19 Jan, 2017 1 commit
-
-
Asmod4n authored
As discussed in #2307
-
- 15 Dec, 2016 1 commit
-
-
Min RK authored
-
- 10 Dec, 2016 1 commit
-
-
Luca Boccassi authored
Solution: fix the check for the socket. This regression happens when using zloop with zmq_pollitem_it with only file descriptors registerted through zloop_poller.
-
- 21 Nov, 2016 1 commit
-
-
Min RK authored
item.fd should be ignored if item.socket is defined. Failing to check .socket could cause false-matches, raising EINVAL in zmq_poller_modify_fd.
-
- 31 Oct, 2016 1 commit
-
-
Hunter Laux authored
This block of code will either return -1 or fall through. The while (true) does nothing. The braces limit the scope of int rc.
-
- 04 Oct, 2016 1 commit
-
-
Luca Boccassi authored
Solution: honor it
-
- 01 Oct, 2016 1 commit
-
-
Nick Guiffrida authored
* Doing so was zmq_poller_poll to always return 0.
-
- 29 Sep, 2016 3 commits
-
-
Min RK authored
This should restore full compatibility with earlier zmq_poll behavior. It complicates things a little bit, as collisions must be detected, and when collisions are found: - event masks must be merged - pollitems, events arrays are no longer co-ordered Reverts the recent zmq_proxy patch to workaround the lack of repeat-item support in zmq_poll that is now fixed.
-
Min RK authored
not -1, ETIMEDOUT like zmq_poller
-
Min RK authored
Return value is the number of events found. This also propagates to the return value of zmq_poller_wait_all. zmq_poller_wait was only returning events on the first-registered socket.
-
- 28 Sep, 2016 2 commits
- 27 Sep, 2016 3 commits
-
-
Min RK authored
instead of allocating a new, identical array and copying the data. This is only safe while zmq_poller_event_t and zmq::socket_poller_t::event_t are the same struct, which they presumably will remain.
-
Min RK authored
avoids unnecessary heap allocations, races on the number of items
-
Min RK authored
Solution: zmq_poller_wait_all signals all events allows signaling multiple events with one call to zmq_poller_wait_all rather than emitting only one event. this prepares for zmq_poll being based on zmq_poller, which requires events for all sockets rather than just one.
-
- 11 Jun, 2016 1 commit
-
-
Michael Lutz authored
Solution: Provide poll() for Windows as well. This is a build option that defaults to off as the resulting binary will only run on Windows Vista or newer. This is not tested with alternative Winsock service providers like VMCI, but the documentation for WSAPoll does not mention limitations. On my local machine, throughput improves by ~10 % (20 simultaneous remote_thr workes to one local_thr, 10 byte messages), while latency improves by ~30 % (measured with remote/local_lat).
-
- 14 May, 2016 1 commit
-
-
evoskuil authored
-
- 12 May, 2016 1 commit
-
-
hitstergtd authored
Solution: - Add checks for **poller_p_ to ensure that we do not segfault when either it or the value within it are NULL - Add tests for the above and increase error state coverage
-
- 04 May, 2016 2 commits
-
-
hitstergtd authored
Solution: Wrap and clean it.
-
Doron Somech authored
-
- 01 May, 2016 1 commit
-
-
hitstergtd authored
Solution: - Add check for the [count] parameter in zmq_sendiov() and zmq_recviov() - Use and add test for zmq_sendiov() in tests/test_iov.cpp - Add error state tests for zmq_sendiov() in tests/test_iov.cpp - Add error state tests for zmq_recviov() in tests/test_iov.cpp - Cleanup tests/test_iov.cpp for style, consistency and clarity - Generally improve test coverage for both API methods Hat-tip: @somdoron, @bluca
-
- 26 Apr, 2016 1 commit
-
-
hitstergtd authored
Solution: fix it
-
- 12 Apr, 2016 1 commit
-
-
Patrik Wenger authored
Solution: use zmq_assert to ensure it's not a nullpointer
-
- 21 Feb, 2016 2 commits
-
-
Luca Boccassi authored
Solution: fix it
-
Osiris authored
Solution: The Coverity Static Code Analyzer was used on libzmq code and found many issues with uninitialized member variables, some redefinition of variables hidding previous instances of same variable name and a couple of functions where return values were not checked, even though all other occurrences were checked (e.g. init_size() return).
-
- 18 Feb, 2016 1 commit
-
-
Osiris authored
Solution: Phase I - make precompiled.hpp be first file included in every source file
-
- 11 Feb, 2016 1 commit
-
-
Pieter Hintjens authored
It's unclear which we need and in the source code, conditional code treats tweetnacl as a subclass of libsodium, which is inaccurate. Solution: redesign the configure/cmake API for this: * tweetnacl is present by default and cannot be enabled * libsodium can be enabled using --with-libsodium, which replaces the built-in tweetnacl * CURVE encryption can be disabled entirely using --enable-curve=no The macros we define in platform.hpp are: ZMQ_HAVE_CURVE 1 // When CURVE is enabled HAVE_LIBSODIUM 1 // When we are using libsodium HAVE_TWEETNACL 1 // When we're using tweetnacl (default) As of this patch, the default build of libzmq always has CURVE security, and always uses tweetnacl.
-
- 09 Feb, 2016 1 commit
-
-
Pieter Hintjens authored
And I'm on a reasonably sized laptop. I think allocating INT_MAX memory is dangerous in a test case. Solution: expose this as a context option. I've used ZMQ_MAX_MSGSZ and documented it and implemented the API. However I don't know how to get the parent context for a socket, so the code in zmq.cpp is still unfinished.
-
- 06 Feb, 2016 1 commit
-
-
Pieter Hintjens authored
Solution: be more explicit in the code, and in the zmq_recv man page (which is the most unobvious case). Assert if length is not zero and buffer is nonetheless null.
-
- 05 Feb, 2016 1 commit
-
-
Brian Silverman authored
It's undefined behavior, and ubsan flags it.
-
- 29 Jan, 2016 1 commit
-
-
somdoron authored
-
- 28 Jan, 2016 1 commit
-
-
Constantin Rack authored
Solution: update to 2016
-
- 27 Jan, 2016 1 commit
-
-
somdoron authored
-
- 20 Jan, 2016 2 commits
-
-
Constantin Rack authored
Solution: include climits Fixes #1720
-
Min RK authored
to avoid overflow for large messages send/recv still succeed for large messages, but `zmq_msg_size` must be used to get the true size.
-
- 29 Dec, 2015 1 commit
-
-
Pieter Hintjens authored
These sockets don't handle multipart data, so if callers send it, they drop frames, and things break silently. Solution: if the caller tries to use ZMQ_SNDMORE, return -1 and set errno to EINVAL.
-
- 21 Dec, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: add these
-