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

Luca Boccassi luca.boccassi at gmail.com
Tue Jan 31 12:41:13 CET 2017


On Mon, 2017-01-30 at 14:18 +0000, Simon.Giesecke at 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 complete tests in our integration environment, I would require a release version. When is 4.2.2 going to be released? Is it possible to do this in the next days?
> 
> Best regards
> Simon

4.2.1 was released 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.boccassi at 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 +0000, Simon.Giesecke at 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 cannot be more precise at the moment; I tried to reproduce the behavioural differences with some reduced code example, but have not been successful so far. To enable me to facilitate a more focused reproduction of the issue, I have a general question in advance. Have there been any deliberate changes in behaviour between 4.1.5 and 4.2.1 that might be related to this? From reading the release notes, I did not find something that raised my attention.
> > 
> > Best regards
> > Simon
> 
> One major change is that setting HWM works also after connecting/binding, is that what you are doing?
> 
> There were many other bug fixes that can be seen in the git log, can't remember all of them off the top of my head
> 
> Also what transport mode are you using?
> 
> Kind regards,
> Luca Boccassi


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20170131/2462e6be/attachment.sig>


More information about the zeromq-dev mailing list