1. 05 Nov, 2018 4 commits
  2. 04 Nov, 2018 8 commits
  3. 02 Nov, 2018 5 commits
  4. 01 Nov, 2018 3 commits
  5. 31 Oct, 2018 4 commits
  6. 30 Oct, 2018 5 commits
  7. 27 Oct, 2018 3 commits
  8. 26 Oct, 2018 3 commits
  9. 22 Oct, 2018 1 commit
  10. 09 Oct, 2018 1 commit
  11. 08 Oct, 2018 3 commits
    • Luca Boccassi's avatar
      Problem: trailing whitespace breaks clang-format-check · cfc9d5f5
      Luca Boccassi authored
      Solution: fix issue introduced by #3270
      cfc9d5f5
    • Luca Boccassi's avatar
      Merge pull request #3271 from gabm/Relicense · b9b325ce
      Luca Boccassi authored
      Problem: gabm didn't signalise his consent to relicense libzmq
      b9b325ce
    • gabm's avatar
      Problem: The flag that indicates the next expected message gets set even if the send fails (#3270) · c1ac158f
      gabm authored
      * ZMQ_DGRAM: flip more flag after successful send
      
      In the dgram socket we have a flag that indicates the next expected message type to ensure that always a pair of "address" + "body" messages gets sent. The first one MUST have the sendmore flag, the second MUST NOT.
      
      In case the message does not get sent because of HWM full, then the function returns EAGAIN as it should. But unfortunately the next expected message type-flag gets flipped as well. When the socket_base::send function now tries to resend the message, it became the wrong message type... If you don't stop sending pairs of messages here (like me) then the next message that gets through will be of the wrong type, which in turn crashes the udp_engine function as described in #3268
      c1ac158f