This version (2017/05/27 13:44) is a draft.
Approvals: 0/1

[00:31:51] * ChanServ sets mode: +o temporalfox [00:54:35] * ChanServ sets mode: +o temporalfox

[02:01:56] *** ChanServ sets mode: +o temporalfox

[08:51:13] <cescoffier> hello pmlopes

[08:51:19] <cescoffier> could you have a look to http://vertx.io/blog/vert-x3-says-hello-to-npm-users/index.html#comment-2137571453

[08:51:26] <pmlopes> hi goodmorning

[08:53:15] <cescoffier> pmlopes temporalfox looks like the is a new version of java, I will re-run automated examples just to see….

[08:53:29] <temporalfox> cescoffier ok

[17:07:09] <jun> hi! i have a short question concerning a potential bug (or a misunderstanding on my side :))

[17:09:54] <jun> it's about asynchronious deployment of verticles. if i call fail on the future object inside the async start method of a verticle, my understanding is that the deployment of the verticle will be considered as failed and vertx will clean up the instance. however, when i stop the program, i see that the stop method of all the “failed” verticles is called…

[17:42:26] <jun> btw, the question above concerns vertx 3.0.0