Approvals: 0/1
[11:04:32] <gateleen_dev> Hi there, does anybody know whether the RedisClient will be updated with features from newer redis versions. Actually I want to use the zadd options which were introduced in redis 3.0.2 but these options seems not to be available in RedisClient
[16:17:36] <BadApe> would it be a really stupid idea to push a 4mb byte array onto the eventbus?
[18:59:15] *** ChanServ sets mode: +o temporal_
[20:46:38] <AlexLehm_> temporal_: interesting, the DNS lookup issue is quite old, that was probably implemented by Tim or Norman and it never worked completely
[20:47:10] <temporal_> AlexLehm_ so it's our DNS implemneation ?
[20:47:16] <temporal_> I thought it was Netty's DNS
[20:47:24] <temporal_> yes it was done before DNS in netty I think
[20:47:35] <temporal_> and it could be reimplemented using Netty's DNS codec
[20:47:36] <AlexLehm_> vert.x is reading the list of record from netty and then is collecting it wrong
[20:47:51] <AlexLehm_> its easy to fix I think
[20:48:20] <AlexLehm_> maybe the netty impl worked differently before, so it might have worked
[20:48:50] <AlexLehm> it depends on the order of the records returned
[20:49:14] <AlexLehm> can I implement a unit test that checks www.yahoo.com?
[20:50:18] <AlexLehm> or rather, would it be stable to use www.yahoo.com in a test?
[20:52:18] <temporal_> AlexLehm yes
[20:52:27] <temporal_> but it might be a non faulty behavior
[20:52:49] <temporal_> the DNS tests use Apache Project
[20:52:58] <temporal_> FakeDNSServer
[20:53:07] <temporal_> wraps org.apache.directory.server.dns.DnsServer
[20:53:11] <temporal_> so you want to look at that
[20:53:17] <temporal_> and provide a reproducer first
[20:53:21] <AlexLehm> ok, that would make sense
[20:53:29] <temporal_> another way to do it
[20:53:30] <temporal_> if you can't
[20:53:41] <temporal_> is to forge DNS UDP requests / response
[21:21:12] <AlexLehm> i think a test with fakednsserver will work
[21:38:27] <temporal_> cool AlexLehm
[21:38:56] <AlexLehm> https://github.com/alexlehm/vert.x/tree/issues/%231752-resolve-cname