Re: [zeromq-dev] Behaviour change between 4.1.5 and 4.2.1?

2017-02-19 Thread brunobodin .
out: > https://github.com/zeromq/libzmq/releases/tag/v4.2.2 > > > > > -Ursprüngliche Nachricht- > > > Von: Luca Boccassi [ > mailto:luca.bocca...@gmail.com ] > > > Gesendet: > Dienstag, 31. Januar 2017 12:41 > > > An: Giesecke, Simo

Re: [zeromq-dev] Behaviour change between 4.1.5 and 4.2.1?

2017-02-19 Thread Kevin Sapper
liche Nachricht- > > > Von: Luca Boccassi [mailto:luca.bocca...@gmail.com] > > > Gesendet: Dienstag, 31. Januar 2017 12:41 > > > An: Giesecke, Simon > > > Cc: zeromq-dev@lists.zeromq.org > > > Betreff: Re: AW: [zeromq-dev] Behaviour change between

Re: [zeromq-dev] Behaviour change between 4.1.5 and 4.2.1?

2017-02-19 Thread Luca Boccassi
the weekend. > > > > > > Kind regards, > > > Luca Boccassi > > > > 4.2.2 is out: https://github.com/zeromq/libzmq/releases/tag/v4.2.2 > > > > > > -----Ursprüngliche Nachricht- > > > > Von: Luca Boccassi [mailto:luca.bocca...@gmail

Re: [zeromq-dev] Behaviour change between 4.1.5 and 4.2.1?

2017-02-18 Thread brunobodin .
[mailto:luca.bocca...@gmail.com] > > > Gesendet: Dienstag, 31. Januar 2017 12:41 > > > An: Giesecke, Simon > > > Cc: zeromq-dev@lists.zeromq.org > > > Betreff: Re: AW: [zeromq-dev] Behaviour change between 4.1.5 and > > > 4.2.1? > > > &g

Re: [zeromq-dev] Behaviour change between 4.1.5 and 4.2.1?

2017-02-18 Thread Luca Boccassi
2 > > -Ursprüngliche Nachricht- > > Von: Luca Boccassi [mailto:luca.bocca...@gmail.com]  > > Gesendet: Dienstag, 31. Januar 2017 12:41 > > An: Giesecke, Simon > > Cc: zeromq-dev@lists.zeromq.org > > Betreff: Re: AW: [zeromq-dev] Behaviour change between 4.1.5 and

Re: [zeromq-dev] Behaviour change between 4.1.5 and 4.2.1?

2017-02-17 Thread Luca Boccassi
not too long ago, so we could probably do one sometimes > before mid February when there should be enough bug fixes queued up > > > -Ursprüngliche Nachricht- > > Von: Luca Boccassi [mailto:luca.bocca...@gmail.com] > > Gesendet: Montag, 16. Januar 2017 12:26 > > An: Z

Re: [zeromq-dev] Behaviour change between 4.1.5 and 4.2.1?

2017-02-17 Thread Simon.Giesecke
Betreff: Re: AW: [zeromq-dev] Behaviour change between 4.1.5 and 4.2.1? On Mon, 2017-01-30 at 14:18 +, simon.giese...@btc-ag.com wrote: > Hi again, > > I was now able to do a local test with the current HEAD of libzmq, which > seems to fix the problem again. > > To do com

Re: [zeromq-dev] Behaviour change between 4.1.5 and 4.2.1?

2017-01-31 Thread Luca Boccassi
rüngliche Nachricht- > Von: Luca Boccassi [mailto:luca.bocca...@gmail.com] > Gesendet: Montag, 16. Januar 2017 12:26 > An: ZeroMQ development list > Betreff: Re: [zeromq-dev] Behaviour change between 4.1.5 and 4.2.1? > > On Mon, 2017-01-16 at 10:32 +, simon.giese...@btc-ag.co

Re: [zeromq-dev] Behaviour change between 4.1.5 and 4.2.1?

2017-01-30 Thread Simon.Giesecke
regards Simon -Ursprüngliche Nachricht- Von: Luca Boccassi [mailto:luca.bocca...@gmail.com] Gesendet: Montag, 16. Januar 2017 12:26 An: ZeroMQ development list Betreff: Re: [zeromq-dev] Behaviour change between 4.1.5 and 4.2.1? On Mon, 2017-01-16 at 10:32 +, simon.giese...@btc-ag.com

Re: [zeromq-dev] Behaviour change between 4.1.5 and 4.2.1?

2017-01-17 Thread Simon.Giesecke
...@gmail.com] Gesendet: Montag, 16. Januar 2017 12:26 An: ZeroMQ development list Betreff: Re: [zeromq-dev] Behaviour change between 4.1.5 and 4.2.1? On Mon, 2017-01-16 at 10:32 +, simon.giese...@btc-ag.com wrote: > Hi, > > we have migrated from ZeroMQ 4.1.5 to 4.2.1 recently and I no

Re: [zeromq-dev] Behaviour change between 4.1.5 and 4.2.1?

2017-01-16 Thread Luca Boccassi
On Mon, 2017-01-16 at 10:32 +, simon.giese...@btc-ag.com wrote: > Hi, > > we have migrated from ZeroMQ 4.1.5 to 4.2.1 recently and I notice some > behaviour change in some of our test cases. These cases are related to > enforcing that some queues run full resp. the HWM is exceeded. Sorry I c

[zeromq-dev] Behaviour change between 4.1.5 and 4.2.1?

2017-01-16 Thread Simon.Giesecke
Hi, we have migrated from ZeroMQ 4.1.5 to 4.2.1 recently and I notice some behaviour change in some of our test cases. These cases are related to enforcing that some queues run full resp. the HWM is exceeded. Sorry I cannot be more precise at the moment; I tried to reproduce the behavioural dif