1. 17 Aug, 2018 1 commit
  2. 15 Aug, 2018 1 commit
  3. 13 Aug, 2018 1 commit
  4. 10 Aug, 2018 1 commit
  5. 09 Aug, 2018 1 commit
  6. 07 Aug, 2018 1 commit
  7. 26 Jul, 2018 1 commit
  8. 30 May, 2018 1 commit
  9. 29 May, 2018 5 commits
  10. 27 May, 2018 1 commit
  11. 26 May, 2018 4 commits
  12. 18 May, 2018 1 commit
  13. 06 Mar, 2018 1 commit
  14. 02 Feb, 2018 1 commit
  15. 23 Oct, 2017 1 commit
  16. 21 Oct, 2017 1 commit
  17. 19 Sep, 2017 2 commits
  18. 07 Sep, 2017 2 commits
  19. 06 Sep, 2017 1 commit
  20. 01 Sep, 2017 1 commit
  21. 14 Jul, 2017 1 commit
    • Marc Sune's avatar
      Fix ROUTER's xhas_out() in MANDATORY mode · b7b89a8f
      Marc Sune authored
      Before this commit, xhas_out() was returning true regardless. This
      was correct before the ZMQ_ROUTER_MANDATORY flag as introduced.
      However, ZMQ_POLLOUT.
      
      With this commit, _if_ ZMQ_ROUTER_MANDATORY is set, xhas_out() will
      return false if ALL peer's outgoing pipes are full.
      
      There is an outstanding high-level design question:
      
      If ZMQ_ROUTER_MANDATORY is set, and zmq_poll() waits for ZMQ_POLLOUT
      events, zmq_poll() will immediately wake up if only 1 pipe has
      room to send, regardless of the peer, creating a busy loop of
      zmq_poll() wake-up, zmq_send() (EAGAIN). There is no way for
      the application to selectively wait for ZMQ_POLLOUT for specific
      peer(s), which seems somehow necessary in ZMQ_ROUTER_MANDATORY.
      
      This discussion will be addressed in a separate issue.
      Signed-off-by: 's avatarMarc Sune <marc@voltanet.io>
      Signed-off-by: 's avatarFredi Raspall <fredi@voltanet.io>
      b7b89a8f
  22. 17 May, 2017 1 commit
    • Luca Boccassi's avatar
      Problem: REP leaves label msgs for dead REQ in pipe · bdc676f6
      Luca Boccassi authored
      Solution: roll back the pipe if writing messages other than the
      first fails in router::xsend. Roll it back also when the pipe is
      terminating.
      Also add test case that reproduces the memory leak when ran with
      valgrind.
      Fixes #2567
      bdc676f6
  23. 16 May, 2017 1 commit
  24. 10 May, 2017 1 commit
  25. 24 Feb, 2017 2 commits
  26. 25 Apr, 2016 1 commit
  27. 21 Feb, 2016 1 commit
    • Osiris's avatar
      Problem: Several problems found by Coverity Static Analyzer · b3d5fa63
      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).
      b3d5fa63
  28. 18 Feb, 2016 1 commit
  29. 07 Feb, 2016 1 commit
  30. 06 Feb, 2016 1 commit