Thanks for your response, I found the issue. I stored some zmq::message_t
objects (C++ high-level binding) in a vector and it turns out I did some
wrong bounds checking:
if (my_vector.size() > 0) { // should be a 1
size_t size = my_vector[1].size(); // example, did some more complex
work
}
So
On libzmq master it's now possible to let travis automatically deploy
artifacts. The deployment is triggered if a new tag is created. I've
created a test release and tag[1] to see if it is working properly. The
files that are available under this release have been deploy by travis.
[1] https://git
Awesome, thanks!
So now if we port this to zeromq4-x and zeromq4-1, we'll just have to
push the tags corresponding to the last commit of each previous release,
right? It might make moving all downloadable to Github a much easier
process.
On Mon, 2016-05-09 at 11:45 +0200, Kevin Sapper wrote:
> On
The deployment has a couple of constraints (see .travis.yml -> deploy: on:
).
One constraint is the repo MUST be "zeromq/libzmq". If we port this to
zeromq4-x and zeromq4-1
we need to adjust this or remove this constraint altogether.
2016-05-09 13:04 GMT+02:00 Luca Boccassi :
> Awesome, thanks!
>
I'm not sure I fully understand the challange, anyway this is what I have
in mind:
Auction server that expose both PUB and ROUTER. Bidders connect to both.
Bidder subscribe to relevant auction. When bidder want to mske a bid it
sending message to the router which process the bid and publish it.
W
On 9/05/16 21:45, Kevin Sapper wrote:
[1] https://github.com/zeromq/libzmq/releases/tag/v4.0.2-test
Thanks for automating this. It looks great.
This gives us two downloads per release (each in .tar.gz and .zip):
https://github.com/zeromq/libzmq/releases/download/v4.0.2-test/zeromq-4.2.0.tar.
Kevin, this is really neat. :)
On Mon, May 9, 2016 at 11:26 PM, Ewen McNeill
wrote:
> On 9/05/16 21:45, Kevin Sapper wrote:
>>
>> [1] https://github.com/zeromq/libzmq/releases/tag/v4.0.2-test
>
>
> Thanks for automating this. It looks great.
>
> This gives us two downloads per release (each in .