Differences

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

Link to this comparison view

irc:1446678000 [2017/05/27 13:44] (current)
Line 1: Line 1:
 +[07:34:51] *** ChanServ sets mode: +o temporalfox
 +
 +[10:58:03] <​ovestoerholt>​ Hi. Anyone here that can provide me with some info about growing usage for Vert.x? When trying to Google it there aren't that many tutorials and examples...
 +
 +[12:33:57] *** ChanServ sets mode: +o temporalfox
 +
 +[17:06:31] <​tsegismont>​ cescoffier, hi, for your devoxx workshop, how do you consume vertx-monitor?​
 +
 +[17:06:51] <​cescoffier>​ tsegismont : I just do a demo as I need to build it
 +
 +[17:07:04] <​cescoffier>​ I've a hawkular bridge that I provide in the source code
 +
 +[17:07:18] <​tsegismont>​ I'm asking because I was about to implement the counter/​gauge separation (currently all values are stored as gauges)
 +
 +[17:07:33] <​cescoffier>​ yes, right now I'm only using gauges
 +
 +[17:07:40] <​tsegismont>​ ok
 +
 +[17:07:54] <​cescoffier>​ but it's just because grafana didn't like the counter
 +
 +[17:08:02] <​cescoffier>​ counter would be nice for actual counter
 +
 +[17:08:07] <​tsegismont>​ then I'll wait a bit
 +
 +[17:08:12] <​cescoffier>​ no no
 +
 +[17:08:15] <​tsegismont>​ so that your demo runs well
 +
 +[17:08:16] <​cescoffier>​ don't worry
 +
 +[17:08:22] <​cescoffier>​ I'm reactive ;-)
 +
 +[17:08:25] <​tsegismont>​ I'll start by updating the grafana plugin
 +
 +[17:08:29] <​tsegismont>​ lol
 +
 +[17:09:47] <​tsegismont>​ also, Julien told me I need to rename the master branch "​initial-work"​ before moving the repo to the vertx org
 +
 +[17:09:51] <​cescoffier>​ so usage of the monitor is a demo I do in front of the attendee (they have business data to implement as exercice just before)
 +
 +[17:10:01] <​cescoffier>​ so I will take the latest version on monday morning
 +
 +[17:10:04] <​tsegismont>​ and announce the move to ask for a review
 +
 +[17:10:08] <​tsegismont>​ I'll do this now
 +
 +[17:10:22] <​tsegismont>​ Then maybe you can tell me how to start CI on the project?
 +
 +[17:10:26] <​cescoffier>​ yes, it's the convention, but we will do that when everything will be merged in
 +
 +[17:10:56] <​cescoffier>​ I've a couple of this to integrate (system property for host and port and enabled)
 +
 +[17:11:01] <​tsegismont>​ ok
 +
 +[17:11:42] <​tsegismont>​ My only concern is that you and/or Julien get enough time before 3.2 to have a look at the code
 +
 +[17:11:52] <​cescoffier>​ I will take the time
 +
 +[17:12:05] <​tsegismont>​ So that, in turn, I get enough time to make changes
 +
 +[17:12:08] <​tsegismont>​ Thanks
 +
 +[17:12:11] <​tsegismont>​ appreciated
 +
 +[17:12:12] <​cescoffier>​ (well actually I did already ;-))
 +
 +[17:12:16] <​tsegismont>​ :P
 +
 +[17:12:43] <​cescoffier>​ I would like to align the property name for all cluster managers
 +
 +[17:13:37] <​cescoffier>​ sorry not cluster manager, metric SPI
 +
 +[17:13:47] <​cescoffier>​ (context switching....)
 +
 +[17:13:51] <​tsegismont>​ :)
 +
 +[17:14:02] <​tsegismont>​ fair enough
 +
 +[17:14:58] <​cescoffier>​ oh yes, I also added the newOptions method in the impl
 +
 +[17:15:02] <​tsegismont>​ there isn't parity in metrics exposed, but agreed
 +
 +[17:15:08] <​cescoffier>​ you need it to enable the metric manager from the command line
 +
 +[17:15:42] <​tsegismont>​ is there a pull request? I got no notificaton
 +
 +[17:19:01] <​cescoffier>​ no, not yet
 +
 +[17:19:09] <​cescoffier>​ right now I try to finish the workshop
 +
 +[17:19:15] <​cescoffier>​ tomorrow it's cleanup time ;-)
 +
 +[17:19:51] <​tsegismont>​ bon courage
 +
 +[17:19:52] <​tsegismont>​ :)
 +
 +[17:21:07] <​cescoffier>​ (unbelievable the time it takes to build a VM with everything....)
 +
 +[18:10:00] <​kislo_metal>​ hi all
 +
 +[18:10:43] <​kislo_metal>​ what are you using for vertx tests? (need kind of chained test)
 +
 +[18:11:40] <​kislo_metal>​ like: put some date with rest vericle, get that data with same rest service
 +
 +[18:15:51] <​kislo_metal>​ no one write integration tests on rest endpoints?
 +
 +[18:39:59] <​kislo_metal>​ what are you using for vertx tests? (need kind of chained test) ike: put some date with rest vericle, get that data with same rest service
 +
 +[19:34:38] <​kislo_metal>​ kislo_metal:​ what are you using for vertx tests? (need kind of chained test) ike: put some date with rest vericle, get that data with same rest service. Thank you
 +
 +[22:10:02] <s0x> hey guys, does anyone know of an approach to add clojure support for vertx 3? Is there a good reason why there is non at the moment?
 +
 +[22:11:39] <​tcrawley>​ s0x: there isn't any currently because there wasn't that much interest/​usage in/of the vertx 2 clojure module
 +
 +[22:12:05] <​tcrawley>​ so I didn't think it was worth the effort to implement, and no one else has said "​I'​ll do it"
 +
 +[22:12:17] <​tcrawley>​ that person could be *you*!
 +
 +[22:13:15] <s0x> This is why I'm asking :)
 +
 +[22:13:20] <​tcrawley>​ cool!
 +
 +[22:14:09] <​tcrawley>​ I haven'​t used vertx 3 at all, so I don't really know what's involved, other than all the other language modules are generated via templates
 +
 +[22:15:18] <s0x> I've seen that... Obviously, need to get used to that first :)
 +
 +[22:16:28] <s0x> Though, I wont promis anything
 +
 +[22:17:19] <​tcrawley>​ heh
 +
 +[23:10:31] <​kislo_metal>​ what are you using for vertx tests? (need kind of chained test) ike: put some date with rest vericle, get that data with same rest service. Thank you
 +
 +[23:10:58] <​Sticky_>​ kislo_metal:​ vertx-unit
 +
 +[23:11:12] <​Sticky_>​ https://​github.com/​vert-x3/​vertx-unit
 +
 +[23:15:28] <​kislo_metal>​ I was trying to use it for last week, but having AssertstionError often- I am using several Async instances (context.async()) - one for PUT call, another for GET
 +
 +[23:16:23] <​kislo_metal>​ so test is not stable..
 +
 +[23:16:53] <​kislo_metal>​ did any one faiced with such issue?
 +
 +[23:17:28] <​Sticky_>​ well only create an async instance for something you plan to complete() at some point
 +
 +[23:18:01] <​Sticky_>​ if you are not going to call complete(), dont create the Async
 +
 +[23:19:32] <​kislo_metal>​ I do call it once I done asserts for http response handler
 +
 +[23:20:39] <​Sticky_>​ well assuming you call complete() on every Async you have created, your test should end. I have never seen it fail
 +
 +[23:21:59] <​kislo_metal>​ the test is working in random way- and same behave for both case: when I run it with maven and from ide test plugins
 +
 +[23:23:24] <​Sticky_>​ are you sure the test framework is to blame, and that your test does not have a race condition?
 +
 +[23:24:18] <​Sticky_>​ if you can paste the test we may have some idea
 +
 +[23:25:45] <​kislo_metal>​ I am not ready to blame framework, just need to hear that if is not standart issue.
 +
 +[23:26:55] <​Sticky_>​ I use vertx-unit reliably, including using multiple Async'​s in a single test, and have not noticed any issues
 +
 +[23:28:03] <​kislo_metal>​ I will try to write the test from begining and came back if I got same issues.
 +
 +[23:28:08] <​kislo_metal>​ Thank you
 +
 +[23:28:24] <​Sticky_>​ no problem