Differences

This shows you the differences between two versions of the page.

Link to this comparison view

irc:1462485600 [2017/05/27 13:44] (current)
Line 1: Line 1:
 +[00:11:00] <​AlexLehm>​ the jenkins starting working again, so the pr is ok with the unit test
 +
 +[01:04:14] *** ChanServ sets mode: +o temporal_
 +
 +[05:14:43] <​kuwv>​ I'm outputting a buffer to a file using writetofile but there is no formatting. Is there a buffer type I should use or should I just add the newline characters to my codec?
 +
 +[15:54:09] <​tsegismont>​ Hi guys. I'm working on vertx-hawkular-metrics,​ adapting to next version changes
 +
 +[15:54:56] <​tsegismont>​ I can't get it working for now, I get NPE when the SPI impl is created
 +
 +[15:55:19] <​tsegismont>​ It happens because in my io.vertx.ext.hawkular.impl.VertxMetricsImpl#​VertxMetricsImpl
 +
 +[15:55:42] <​tsegismont>​ I try to get a Context instance with #​getOrCreateContext
 +
 +[15:56:20] <​tsegismont>​ but with the latest changes
 +
 +[15:56:22] <​tsegismont>​ io.vertx.core.impl.ContextImpl#​ContextImpl
 +
 +[15:56:47] <​tsegismont>​ needs the internalBlockingPool to be ready
 +
 +[15:56:59] <​tsegismont>​ but when the Metrics implementation is loaded
 +
 +[15:57:34] <​tsegismont>​ the internal blocking pool as not been created yet
 +
 +[15:57:51] <​tsegismont>​ it's not the first time I have this kind of issue
 +
 +[15:59:01] <​tsegismont>​ and I wonder if we could have a callback in io.vertx.core.spi.metrics.VertxMetrics
 +
 +[15:59:15] <​tsegismont>​ to indicate that the vertx instance is fully initialized
 +
 +[15:59:33] <​tsegismont>​ so that spi implementors can safely start using it
 +
 +[15:59:43] <​tsegismont>​ WDYT?
 +
 +[16:48:48] <​tsegismont>​ I'll use io.vertx.core.spi.metrics.VertxMetrics#​eventBusInitialized
 +
 +[20:13:57] *** ChanServ sets mode: +o temporalfox
 +
 +[20:18:17] <​Yakabu>​ Hi. In this talk (https://​www.youtube.com/​watch?​v=EMtoN9wFEOU),​ Tim mentions that vert.x 3.0 will feature something similar to supervision trees. Does this feature exist?
 +
 +[20:22:17] <​Yakabu>​ I'm looking to build a hierarchically structured application,​ with many distributed nodes connected over TCP/​websocket. I'd like to manage the control of nodes with each node having a parent. Is this usecase suitable for vert.x?
 +
 +[22:52:17] *** ChanServ sets mode: +o temporal_