Sporadic test failure: io.netty.resolver.dns.DnsNameResolverTest.testResolveA

Does anybody see this error locally? I can't reproduce it so far and I have no clue. /cc @normanmaurer @Scottmitch
Error Message:
Expected: is <people.com.cn/<IP_ADDRESS>>
     but: was <people.com.cn/<IP_ADDRESS>>

Stacktrace:
java.lang.AssertionError:
Expected: is <people.com.cn/<IP_ADDRESS>>
     but: was <people.com.cn/<IP_ADDRESS>>
	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
	at org.junit.Assert.assertThat(Assert.java:865)
	at org.junit.Assert.assertThat(Assert.java:832)
	at io.netty.resolver.dns.DnsNameResolverTest.testResolveA(DnsNameResolverTest.java:294)

Standard Output:
05:48:33.399 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [22251: /<IP_ADDRESS>:53], DnsQuestion(name: google.com, type: A, class: IN)
05:48:33.400 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [24180: /<IP_ADDRESS>:53], DnsQuestion(name: facebook.com, type: A, class: IN)
05:48:33.400 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [49226: /<IP_ADDRESS>:53], DnsQuestion(name: youtube.com, type: A, class: IN)
05:48:33.400 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [32663: /<IP_ADDRESS>:53], DnsQuestion(name: yahoo.com, type: A, class: IN)
05:48:33.400 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [48513: /<IP_ADDRESS>:53], DnsQuestion(name: baidu.com, type: A, class: IN)
05:48:33.400 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [10737: /<IP_ADDRESS>:53], DnsQuestion(name: wikipedia.org, type: A, class: IN)
05:48:33.401 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [50030: /<IP_ADDRESS>:53], DnsQuestion(name: amazon.com, type: A, class: IN)
05:48:33.401 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [24076: /<IP_ADDRESS>:53], DnsQuestion(name: twitter.com, type: A, class: IN)
05:48:33.401 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [42936: /<IP_ADDRESS>:53], DnsQuestion(name: qq.com, type: A, class: IN)
05:48:33.401 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [9815: /<IP_ADDRESS>:53], DnsQuestion(name: taobao.com, type: A, class: IN)
05:48:33.401 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [64139: /<IP_ADDRESS>:53], DnsQuestion(name: linkedin.com, type: A, class: IN)
05:48:33.401 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [2061: /<IP_ADDRESS>:53], DnsQuestion(name: google.co.in, type: A, class: IN)
05:48:33.402 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [33522: /<IP_ADDRESS>:53], DnsQuestion(name: live.com, type: A, class: IN)
05:48:33.402 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [51015: /<IP_ADDRESS>:53], DnsQuestion(name: hao123.com, type: A, class: IN)
05:48:33.402 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [52957: /<IP_ADDRESS>:53], DnsQuestion(name: sina.com.cn, type: A, class: IN)
05:48:33.402 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [36657: /<IP_ADDRESS>:53], DnsQuestion(name: blogspot.com, type: A, class: IN)
05:48:33.402 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [1989: /<IP_ADDRESS>:53], DnsQuestion(name: weibo.com, type: A, class: IN)
05:48:33.403 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [53087: /<IP_ADDRESS>:53], DnsQuestion(name: yahoo.co.jp, type: A, class: IN)
05:48:33.403 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [31990: /<IP_ADDRESS>:53], DnsQuestion(name: tmall.com, type: A, class: IN)
05:48:33.407 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [24397: /<IP_ADDRESS>:53], DnsQuestion(name: yandex.ru, type: A, class: IN)
05:48:33.407 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [38015: /<IP_ADDRESS>:53], DnsQuestion(name: sohu.com, type: A, class: IN)
05:48:33.407 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [47356: /<IP_ADDRESS>:53], DnsQuestion(name: bing.com, type: A, class: IN)
05:48:33.407 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [5056: /<IP_ADDRESS>:53], DnsQuestion(name: ebay.com, type: A, class: IN)
05:48:33.407 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [23480: /<IP_ADDRESS>:53], DnsQuestion(name: pinterest.com, type: A, class: IN)
05:48:33.408 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [61607: /<IP_ADDRESS>:53], DnsQuestion(name: vk.com, type: A, class: IN)
05:48:33.408 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [43007: /<IP_ADDRESS>:53], DnsQuestion(name: google.de, type: A, class: IN)
05:48:33.408 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [7296: /<IP_ADDRESS>:53], DnsQuestion(name: wordpress.com, type: A, class: IN)
05:48:33.408 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [50572: /<IP_ADDRESS>:53], DnsQuestion(name: apple.com, type: A, class: IN)
05:48:33.409 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [63871: /<IP_ADDRESS>:53], DnsQuestion(name: google.co.jp, type: A, class: IN)
05:48:33.409 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [25739: /<IP_ADDRESS>:53], DnsQuestion(name: google.co.uk, type: A, class: IN)
05:48:33.409 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [27607: /<IP_ADDRESS>:53], DnsQuestion(name: 360.cn, type: A, class: IN)
05:48:33.409 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [27367: /<IP_ADDRESS>:53], DnsQuestion(name: instagram.com, type: A, class: IN)
05:48:33.411 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [46984: /<IP_ADDRESS>:53], DnsQuestion(name: google.fr, type: A, class: IN)
05:48:33.411 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [57033: /<IP_ADDRESS>:53], DnsQuestion(name: msn.com, type: A, class: IN)
05:48:33.411 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [39876: /<IP_ADDRESS>:53], DnsQuestion(name: ask.com, type: A, class: IN)
05:48:33.411 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [40750: /<IP_ADDRESS>:53], DnsQuestion(name: soso.com, type: A, class: IN)
05:48:33.411 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [23808: /<IP_ADDRESS>:53], DnsQuestion(name: google.com.br, type: A, class: IN)
05:48:33.411 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [48043: /<IP_ADDRESS>:53], DnsQuestion(name: tumblr.com, type: A, class: IN)
05:48:33.412 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [44710: /<IP_ADDRESS>:53], DnsQuestion(name: paypal.com, type: A, class: IN)
05:48:33.412 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [31824: /<IP_ADDRESS>:53], DnsQuestion(name: mail.ru, type: A, class: IN)
05:48:33.412 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [44393: /<IP_ADDRESS>:53], DnsQuestion(name: xvideos.com, type: A, class: IN)
05:48:33.412 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [27309: /<IP_ADDRESS>:53], DnsQuestion(name: microsoft.com, type: A, class: IN)
05:48:33.413 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [23361: /<IP_ADDRESS>:53], DnsQuestion(name: google.ru, type: A, class: IN)
05:48:33.413 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [60677: /<IP_ADDRESS>:53], DnsQuestion(name: reddit.com, type: A, class: IN)
05:48:33.413 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [19975: /<IP_ADDRESS>:53], DnsQuestion(name: google.it, type: A, class: IN)
05:48:33.413 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [17558: /<IP_ADDRESS>:53], DnsQuestion(name: imgur.com, type: A, class: IN)
05:48:33.413 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [33210: /<IP_ADDRESS>:53], DnsQuestion(name: 163.com, type: A, class: IN)
05:48:33.414 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [20: /<IP_ADDRESS>:53], DnsQuestion(name: google.es, type: A, class: IN)
05:48:33.414 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [32611: /<IP_ADDRESS>:53], DnsQuestion(name: imdb.com, type: A, class: IN)
05:48:33.414 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [13115: /<IP_ADDRESS>:53], DnsQuestion(name: aliexpress.com, type: A, class: IN)
05:48:33.414 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [18847: /<IP_ADDRESS>:53], DnsQuestion(name: t.co, type: A, class: IN)
05:48:33.414 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [1169: /<IP_ADDRESS>:53], DnsQuestion(name: go.com, type: A, class: IN)
05:48:33.414 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [49102: /<IP_ADDRESS>:53], DnsQuestion(name: adcash.com, type: A, class: IN)
05:48:33.415 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [25153: /<IP_ADDRESS>:53], DnsQuestion(name: craigslist.org, type: A, class: IN)
05:48:33.415 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [26853: /<IP_ADDRESS>:53], DnsQuestion(name: amazon.co.jp, type: A, class: IN)
05:48:33.415 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [61218: /<IP_ADDRESS>:53], DnsQuestion(name: alibaba.com, type: A, class: IN)
05:48:33.415 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [55010: /<IP_ADDRESS>:53], DnsQuestion(name: google.com.mx, type: A, class: IN)
05:48:33.415 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [30943: /<IP_ADDRESS>:53], DnsQuestion(name: stackoverflow.com, type: A, class: IN)
05:48:33.415 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [5099: /<IP_ADDRESS>:53], DnsQuestion(name: xhamster.com, type: A, class: IN)
05:48:33.416 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [34880: /<IP_ADDRESS>:53], DnsQuestion(name: fc2.com, type: A, class: IN)
05:48:33.416 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [51718: /<IP_ADDRESS>:53], DnsQuestion(name: google.ca, type: A, class: IN)
05:48:33.416 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [56479: /<IP_ADDRESS>:53], DnsQuestion(name: bbc.co.uk, type: A, class: IN)
05:48:33.417 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [5758: /<IP_ADDRESS>:53], DnsQuestion(name: espn.go.com, type: A, class: IN)
05:48:33.417 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [58232: /<IP_ADDRESS>:53], DnsQuestion(name: cnn.com, type: A, class: IN)
05:48:33.417 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [14827: /<IP_ADDRESS>:53], DnsQuestion(name: google.co.id, type: A, class: IN)
05:48:33.418 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [32035: /<IP_ADDRESS>:53], DnsQuestion(name: people.com.cn, type: A, class: IN)
05:48:33.418 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [38360: /<IP_ADDRESS>:53], DnsQuestion(name: gmw.cn, type: A, class: IN)
05:48:33.418 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [40880: /<IP_ADDRESS>:53], DnsQuestion(name: pornhub.com, type: A, class: IN)
05:48:33.418 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [43285: /<IP_ADDRESS>:53], DnsQuestion(name: blogger.com, type: A, class: IN)
05:48:33.419 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [43236: /<IP_ADDRESS>:53], DnsQuestion(name: huffingtonpost.com, type: A, class: IN)
05:48:33.419 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [64421: /<IP_ADDRESS>:53], DnsQuestion(name: flipkart.com, type: A, class: IN)
05:48:33.419 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [28771: /<IP_ADDRESS>:53], DnsQuestion(name: google.com.tr, type: A, class: IN)
05:48:33.419 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [11095: /<IP_ADDRESS>:53], DnsQuestion(name: amazon.de, type: A, class: IN)
05:48:33.419 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [27379: /<IP_ADDRESS>:53], DnsQuestion(name: netflix.com, type: A, class: IN)
05:48:33.420 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [35329: /<IP_ADDRESS>:53], DnsQuestion(name: onclickads.net, type: A, class: IN)
05:48:33.420 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [28650: /<IP_ADDRESS>:53], DnsQuestion(name: kickass.to, type: A, class: IN)
05:48:33.420 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [65113: /<IP_ADDRESS>:53], DnsQuestion(name: google.com.au, type: A, class: IN)
05:48:33.420 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [61887: /<IP_ADDRESS>:53], DnsQuestion(name: google.pl, type: A, class: IN)
05:48:33.420 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [6270: /<IP_ADDRESS>:53], DnsQuestion(name: xinhuanet.com, type: A, class: IN)
05:48:33.420 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [47803: /<IP_ADDRESS>:53], DnsQuestion(name: ebay.de, type: A, class: IN)
05:48:33.421 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [35608: /<IP_ADDRESS>:53], DnsQuestion(name: wordpress.org, type: A, class: IN)
05:48:33.421 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [32469: /<IP_ADDRESS>:53], DnsQuestion(name: odnoklassniki.ru, type: A, class: IN)
05:48:33.421 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [31268: /<IP_ADDRESS>:53], DnsQuestion(name: google.com.hk, type: A, class: IN)
05:48:33.421 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [54185: /<IP_ADDRESS>:53], DnsQuestion(name: adobe.com, type: A, class: IN)
05:48:33.421 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [20582: /<IP_ADDRESS>:53], DnsQuestion(name: dailymotion.com, type: A, class: IN)
05:48:33.422 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [24480: /<IP_ADDRESS>:53], DnsQuestion(name: dailymail.co.uk, type: A, class: IN)
05:48:33.422 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [3189: /<IP_ADDRESS>:53], DnsQuestion(name: indiatimes.com, type: A, class: IN)
05:48:33.422 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [20778: /<IP_ADDRESS>:53], DnsQuestion(name: thepiratebay.se, type: A, class: IN)
05:48:33.422 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [13939: /<IP_ADDRESS>:53], DnsQuestion(name: amazon.co.uk, type: A, class: IN)
05:48:33.422 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [28463: /<IP_ADDRESS>:53], DnsQuestion(name: xnxx.com, type: A, class: IN)
05:48:33.423 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [61289: /<IP_ADDRESS>:53], DnsQuestion(name: rakuten.co.jp, type: A, class: IN)
05:48:33.423 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [21396: /<IP_ADDRESS>:53], DnsQuestion(name: dropbox.com, type: A, class: IN)
05:48:33.423 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [52037: /<IP_ADDRESS>:53], DnsQuestion(name: tudou.com, type: A, class: IN)
05:48:33.423 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [41203: /<IP_ADDRESS>:53], DnsQuestion(name: about.com, type: A, class: IN)
05:48:33.423 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [26234: /<IP_ADDRESS>:53], DnsQuestion(name: cnet.com, type: A, class: IN)
05:48:33.424 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [17510: /<IP_ADDRESS>:53], DnsQuestion(name: vimeo.com, type: A, class: IN)
05:48:33.424 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [59461: /<IP_ADDRESS>:53], DnsQuestion(name: redtube.com, type: A, class: IN)
05:48:33.424 [main] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] WRITE: [5253: /<IP_ADDRESS>:53], DnsQuestion(name: blogspot.in, type: A, class: IN)
05:48:33.430 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [10737: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@a9b2eeb
05:48:33.431 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [24076: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@2de189c0
05:48:33.431 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [52957: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@66f9be6c
05:48:33.432 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [50030: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@5a9960de
05:48:33.432 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [48513: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@926e110
05:48:33.434 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [42936: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@28a8d67d
05:48:33.435 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [22251: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@38917da
05:48:33.435 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.com: <IP_ADDRESS>
05:48:33.435 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [24397: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@120708e5
05:48:33.435 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [38015: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@2c9755d4
05:48:33.436 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [49226: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@42627505
05:48:33.437 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [64139: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@99e9d54
05:48:33.437 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [47356: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@2374fca2
05:48:33.438 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [2061: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@35db24ed
05:48:33.438 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [43007: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@64c0b50e
05:48:33.439 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [50572: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@1949e0ff
05:48:33.439 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [31990: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@1ddc9e98
05:48:33.440 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [27367: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@71cc2d82
05:48:33.440 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [7296: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@10459e70
05:48:33.441 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [23480: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@465dca9f
05:48:33.441 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [63871: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@3f8cb492
05:48:33.442 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [19975: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@2fbc3edc
05:48:33.443 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [23361: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@13369345
05:48:33.444 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [18847: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@3b97aa8e
05:48:33.445 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [49102: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@6165b14a
05:48:33.445 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [1169: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@2fe12964
05:48:33.445 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [27309: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@8ea2b66
05:48:33.446 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [33522: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@e2f332f
05:48:33.446 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [40750: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@428c3c41
05:48:33.447 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [25739: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@6480977d
05:48:33.447 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [26853: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@3d682190
05:48:33.448 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [5758: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@4aa9cb59
05:48:33.449 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [60677: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@69e48879
05:48:33.450 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [13115: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@93fd147
05:48:33.450 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [56479: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@75a71551
05:48:33.451 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [46984: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@71d0fbbf
05:48:33.451 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [17558: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@3cba12bc
05:48:33.451 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [40880: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@4bf85985
05:48:33.453 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [61218: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@638c036
05:48:33.453 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [58232: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@70c3de4d
05:48:33.453 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [28771: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@1c800d1b
05:48:33.454 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [54185: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@153d4b7f
05:48:33.455 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [28650: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@5544109e
05:48:33.455 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [35329: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@3b1b8dcd
05:48:33.455 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [55010: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@27efa760
05:48:33.456 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [5056: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@58f66651
05:48:33.457 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [48043: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@2dc35d31
05:48:33.457 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [57033: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@4ad1c8a1
05:48:33.458 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [5099: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@10dfb23c
05:48:33.458 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [32035: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@7b708a98
05:48:33.459 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [43236: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@4c6d6a12
05:48:33.460 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [24480: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@83d27fe
05:48:33.460 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [14827: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@651e3a97
05:48:33.461 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [20778: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@1a4558e6
05:48:33.461 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [23808: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@3ddf9c46
05:48:33.462 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [64421: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@5c3c5ed4
05:48:33.462 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [30943: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@48621d46
05:48:33.463 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [27379: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@78d0eec4
05:48:33.463 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [28463: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@39ac6034
05:48:33.464 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [32469: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@7d8432b
05:48:33.465 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [20582: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@5f88e6bb
05:48:33.465 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [35608: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@20519540
05:48:33.465 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [61887: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@7a26ecbe
05:48:33.466 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [24180: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@3f2239ca
05:48:33.466 [main] INFO  i.netty.resolver.dns.DnsNameResolver - facebook.com: <IP_ADDRESS>
05:48:33.466 [main] INFO  i.netty.resolver.dns.DnsNameResolver - youtube.com: <IP_ADDRESS>
05:48:33.466 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [32663: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@2707adab
05:48:33.466 [main] INFO  i.netty.resolver.dns.DnsNameResolver - yahoo.com: <IP_ADDRESS>
05:48:33.466 [main] INFO  i.netty.resolver.dns.DnsNameResolver - baidu.com: <IP_ADDRESS>
05:48:33.467 [main] INFO  i.netty.resolver.dns.DnsNameResolver - wikipedia.org: <IP_ADDRESS>
05:48:33.467 [main] INFO  i.netty.resolver.dns.DnsNameResolver - amazon.com: <IP_ADDRESS>
05:48:33.467 [main] INFO  i.netty.resolver.dns.DnsNameResolver - twitter.com: <IP_ADDRESS>
05:48:33.467 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [59461: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@bd0c79e
05:48:33.467 [main] INFO  i.netty.resolver.dns.DnsNameResolver - qq.com: <IP_ADDRESS>
05:48:33.467 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [51015: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@46de9946
05:48:33.468 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [20: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@689c143e
05:48:33.468 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [13939: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@72ec9673
05:48:33.468 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [41203: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@7f8d5387
05:48:33.469 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [34880: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@4d2be199
05:48:33.469 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [43285: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@451e21e6
05:48:33.470 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [52037: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@53d76838
05:48:33.470 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [5253: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@46d318ae
05:48:33.471 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [61607: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@54661ec4
05:48:33.471 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [47803: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@604304bf
05:48:33.471 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [61289: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@83d2627
05:48:33.472 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [44393: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@56f559e6
05:48:33.479 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [44710: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@3281edc2
05:48:33.481 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [6270: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@4a1f71d1
05:48:33.481 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [36657: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@2bf27aab
05:48:33.483 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [3189: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@57b42c5a
05:48:33.493 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [65113: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@6a663493
05:48:33.497 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [26234: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@5bc651f7
05:48:33.499 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [11095: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@63595f06
05:48:33.503 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [51718: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@157969cb
05:48:33.511 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [31268: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@4ee0055b
05:48:33.515 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [39876: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@27c0ac99
05:48:33.535 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [31824: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@e486608
05:48:33.596 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [32611: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@50a1613b
05:48:33.612 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [25153: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@1e256ca9
05:48:33.637 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [17510: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@3ca3bf90
05:48:33.661 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [21396: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@7196f62a
05:48:33.772 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [53087: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@2ae5f99a
05:48:33.778 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [38360: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@1f10984b
05:48:33.955 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [27607: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@3eeeeb06
05:48:33.990 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [9815: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@788f6d57
05:48:33.990 [main] INFO  i.netty.resolver.dns.DnsNameResolver - taobao.com: <IP_ADDRESS>
05:48:33.990 [main] INFO  i.netty.resolver.dns.DnsNameResolver - linkedin.com: <IP_ADDRESS>
05:48:33.990 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.co.in: <IP_ADDRESS>
05:48:33.990 [main] INFO  i.netty.resolver.dns.DnsNameResolver - live.com: <IP_ADDRESS>
05:48:33.990 [main] INFO  i.netty.resolver.dns.DnsNameResolver - hao123.com: <IP_ADDRESS>
05:48:33.990 [main] INFO  i.netty.resolver.dns.DnsNameResolver - sina.com.cn: <IP_ADDRESS>
05:48:33.990 [main] INFO  i.netty.resolver.dns.DnsNameResolver - blogspot.com: <IP_ADDRESS>
05:48:34.133 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [9232: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@7da362f5
05:48:34.159 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [1989: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@666a7fca
05:48:34.159 [main] INFO  i.netty.resolver.dns.DnsNameResolver - weibo.com: <IP_ADDRESS>
05:48:34.160 [main] INFO  i.netty.resolver.dns.DnsNameResolver - yahoo.co.jp: <IP_ADDRESS>
05:48:34.160 [main] INFO  i.netty.resolver.dns.DnsNameResolver - tmall.com: <IP_ADDRESS>
05:48:34.160 [main] INFO  i.netty.resolver.dns.DnsNameResolver - yandex.ru: <IP_ADDRESS>
05:48:34.160 [main] INFO  i.netty.resolver.dns.DnsNameResolver - sohu.com: <IP_ADDRESS>
05:48:34.160 [main] INFO  i.netty.resolver.dns.DnsNameResolver - bing.com: <IP_ADDRESS>
05:48:34.160 [main] INFO  i.netty.resolver.dns.DnsNameResolver - ebay.com: <IP_ADDRESS>
05:48:34.160 [main] INFO  i.netty.resolver.dns.DnsNameResolver - pinterest.com: <IP_ADDRESS>
05:48:34.160 [main] INFO  i.netty.resolver.dns.DnsNameResolver - vk.com: <IP_ADDRESS>
05:48:34.160 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.de: <IP_ADDRESS>
05:48:34.161 [main] INFO  i.netty.resolver.dns.DnsNameResolver - wordpress.com: <IP_ADDRESS>
05:48:34.161 [main] INFO  i.netty.resolver.dns.DnsNameResolver - apple.com: <IP_ADDRESS>
05:48:34.161 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.co.jp: <IP_ADDRESS>
05:48:34.161 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.co.uk: <IP_ADDRESS>
05:48:34.161 [main] INFO  i.netty.resolver.dns.DnsNameResolver - 360.cn: <IP_ADDRESS>
05:48:34.161 [main] INFO  i.netty.resolver.dns.DnsNameResolver - instagram.com: <IP_ADDRESS>
05:48:34.161 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.fr: <IP_ADDRESS>
05:48:34.161 [main] INFO  i.netty.resolver.dns.DnsNameResolver - msn.com: <IP_ADDRESS>
05:48:34.161 [main] INFO  i.netty.resolver.dns.DnsNameResolver - ask.com: <IP_ADDRESS>
05:48:34.161 [main] INFO  i.netty.resolver.dns.DnsNameResolver - soso.com: <IP_ADDRESS>
05:48:34.161 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.com.br: <IP_ADDRESS>
05:48:34.161 [main] INFO  i.netty.resolver.dns.DnsNameResolver - tumblr.com: <IP_ADDRESS>
05:48:34.161 [main] INFO  i.netty.resolver.dns.DnsNameResolver - paypal.com: <IP_ADDRESS>
05:48:34.161 [main] INFO  i.netty.resolver.dns.DnsNameResolver - mail.ru: <IP_ADDRESS>
05:48:34.161 [main] INFO  i.netty.resolver.dns.DnsNameResolver - xvideos.com: <IP_ADDRESS>
05:48:34.161 [main] INFO  i.netty.resolver.dns.DnsNameResolver - microsoft.com: <IP_ADDRESS>
05:48:34.162 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.ru: <IP_ADDRESS>
05:48:34.162 [main] INFO  i.netty.resolver.dns.DnsNameResolver - reddit.com: <IP_ADDRESS>
05:48:34.162 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.it: <IP_ADDRESS>
05:48:34.162 [main] INFO  i.netty.resolver.dns.DnsNameResolver - imgur.com: <IP_ADDRESS>
05:48:34.617 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [35652: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@2f951eda
05:48:35.545 [nioEventLoopGroup-0-0] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x372cc422, /0:0:0:0:0:0:0:0:52175] RECEIVED: [33210: /<IP_ADDRESS>:53], io.netty.handler.codec.dns.DnsResponse@2c732baa
05:48:35.545 [main] INFO  i.netty.resolver.dns.DnsNameResolver - 163.com: <IP_ADDRESS>
05:48:35.545 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.es: <IP_ADDRESS>
05:48:35.545 [main] INFO  i.netty.resolver.dns.DnsNameResolver - imdb.com: <IP_ADDRESS>
05:48:35.545 [main] INFO  i.netty.resolver.dns.DnsNameResolver - aliexpress.com: <IP_ADDRESS>
05:48:35.545 [main] INFO  i.netty.resolver.dns.DnsNameResolver - t.co: <IP_ADDRESS>
05:48:35.545 [main] INFO  i.netty.resolver.dns.DnsNameResolver - go.com: <IP_ADDRESS>
05:48:35.545 [main] INFO  i.netty.resolver.dns.DnsNameResolver - adcash.com: <IP_ADDRESS>
05:48:35.546 [main] INFO  i.netty.resolver.dns.DnsNameResolver - craigslist.org: <IP_ADDRESS>
05:48:35.546 [main] INFO  i.netty.resolver.dns.DnsNameResolver - amazon.co.jp: <IP_ADDRESS>
05:48:35.546 [main] INFO  i.netty.resolver.dns.DnsNameResolver - alibaba.com: <IP_ADDRESS>
05:48:35.546 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.com.mx: <IP_ADDRESS>
05:48:35.546 [main] INFO  i.netty.resolver.dns.DnsNameResolver - stackoverflow.com: <IP_ADDRESS>
05:48:35.546 [main] INFO  i.netty.resolver.dns.DnsNameResolver - xhamster.com: <IP_ADDRESS>
05:48:35.546 [main] INFO  i.netty.resolver.dns.DnsNameResolver - fc2.com: <IP_ADDRESS>
05:48:35.546 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.ca: <IP_ADDRESS>
05:48:35.546 [main] INFO  i.netty.resolver.dns.DnsNameResolver - bbc.co.uk: <IP_ADDRESS>
05:48:35.546 [main] INFO  i.netty.resolver.dns.DnsNameResolver - espn.go.com: <IP_ADDRESS>
05:48:35.546 [main] INFO  i.netty.resolver.dns.DnsNameResolver - cnn.com: <IP_ADDRESS>
05:48:35.546 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.co.id: <IP_ADDRESS>
05:48:35.546 [main] INFO  i.netty.resolver.dns.DnsNameResolver - people.com.cn: <IP_ADDRESS>
05:48:35.546 [main] INFO  i.netty.resolver.dns.DnsNameResolver - gmw.cn: <IP_ADDRESS>
05:48:35.546 [main] INFO  i.netty.resolver.dns.DnsNameResolver - pornhub.com: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - blogger.com: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - huffingtonpost.com: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - flipkart.com: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.com.tr: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - amazon.de: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - netflix.com: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - onclickads.net: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - kickass.to: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.com.au: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.pl: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - xinhuanet.com: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - ebay.de: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - wordpress.org: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - odnoklassniki.ru: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.com.hk: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - adobe.com: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - dailymotion.com: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - dailymail.co.uk: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - indiatimes.com: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - thepiratebay.se: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - amazon.co.uk: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - xnxx.com: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - rakuten.co.jp: <IP_ADDRESS>
05:48:35.547 [main] INFO  i.netty.resolver.dns.DnsNameResolver - dropbox.com: <IP_ADDRESS>
05:48:35.548 [main] INFO  i.netty.resolver.dns.DnsNameResolver - tudou.com: <IP_ADDRESS>
05:48:35.548 [main] INFO  i.netty.resolver.dns.DnsNameResolver - about.com: <IP_ADDRESS>
05:48:35.548 [main] INFO  i.netty.resolver.dns.DnsNameResolver - cnet.com: <IP_ADDRESS>
05:48:35.548 [main] INFO  i.netty.resolver.dns.DnsNameResolver - vimeo.com: <IP_ADDRESS>
05:48:35.548 [main] INFO  i.netty.resolver.dns.DnsNameResolver - redtube.com: <IP_ADDRESS>
05:48:35.548 [main] INFO  i.netty.resolver.dns.DnsNameResolver - blogspot.in: <IP_ADDRESS>
05:48:35.554 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.com: <IP_ADDRESS>
05:48:35.554 [main] INFO  i.netty.resolver.dns.DnsNameResolver - facebook.com: <IP_ADDRESS>
05:48:35.555 [main] INFO  i.netty.resolver.dns.DnsNameResolver - youtube.com: <IP_ADDRESS>
05:48:35.556 [main] INFO  i.netty.resolver.dns.DnsNameResolver - yahoo.com: <IP_ADDRESS>
05:48:35.556 [main] INFO  i.netty.resolver.dns.DnsNameResolver - baidu.com: <IP_ADDRESS>
05:48:35.556 [main] INFO  i.netty.resolver.dns.DnsNameResolver - wikipedia.org: <IP_ADDRESS>
05:48:35.556 [main] INFO  i.netty.resolver.dns.DnsNameResolver - amazon.com: <IP_ADDRESS>
05:48:35.556 [main] INFO  i.netty.resolver.dns.DnsNameResolver - twitter.com: <IP_ADDRESS>
05:48:35.556 [main] INFO  i.netty.resolver.dns.DnsNameResolver - qq.com: <IP_ADDRESS>
05:48:35.561 [main] INFO  i.netty.resolver.dns.DnsNameResolver - taobao.com: <IP_ADDRESS>
05:48:35.561 [main] INFO  i.netty.resolver.dns.DnsNameResolver - linkedin.com: <IP_ADDRESS>
05:48:35.561 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.co.in: <IP_ADDRESS>
05:48:35.561 [main] INFO  i.netty.resolver.dns.DnsNameResolver - live.com: <IP_ADDRESS>
05:48:35.561 [main] INFO  i.netty.resolver.dns.DnsNameResolver - hao123.com: <IP_ADDRESS>
05:48:35.561 [main] INFO  i.netty.resolver.dns.DnsNameResolver - sina.com.cn: <IP_ADDRESS>
05:48:35.561 [main] INFO  i.netty.resolver.dns.DnsNameResolver - blogspot.com: <IP_ADDRESS>
05:48:35.561 [main] INFO  i.netty.resolver.dns.DnsNameResolver - weibo.com: <IP_ADDRESS>
05:48:35.562 [main] INFO  i.netty.resolver.dns.DnsNameResolver - yahoo.co.jp: <IP_ADDRESS>
05:48:35.562 [main] INFO  i.netty.resolver.dns.DnsNameResolver - tmall.com: <IP_ADDRESS>
05:48:35.562 [main] INFO  i.netty.resolver.dns.DnsNameResolver - yandex.ru: <IP_ADDRESS>
05:48:35.562 [main] INFO  i.netty.resolver.dns.DnsNameResolver - sohu.com: <IP_ADDRESS>
05:48:35.562 [main] INFO  i.netty.resolver.dns.DnsNameResolver - bing.com: <IP_ADDRESS>
05:48:35.562 [main] INFO  i.netty.resolver.dns.DnsNameResolver - ebay.com: <IP_ADDRESS>
05:48:35.562 [main] INFO  i.netty.resolver.dns.DnsNameResolver - pinterest.com: <IP_ADDRESS>
05:48:35.562 [main] INFO  i.netty.resolver.dns.DnsNameResolver - vk.com: <IP_ADDRESS>
05:48:35.562 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.de: <IP_ADDRESS>
05:48:35.563 [main] INFO  i.netty.resolver.dns.DnsNameResolver - wordpress.com: <IP_ADDRESS>
05:48:35.563 [main] INFO  i.netty.resolver.dns.DnsNameResolver - apple.com: <IP_ADDRESS>
05:48:35.563 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.co.jp: <IP_ADDRESS>
05:48:35.563 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.co.uk: <IP_ADDRESS>
05:48:35.564 [main] INFO  i.netty.resolver.dns.DnsNameResolver - 360.cn: <IP_ADDRESS>
05:48:35.564 [main] INFO  i.netty.resolver.dns.DnsNameResolver - instagram.com: <IP_ADDRESS>
05:48:35.564 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.fr: <IP_ADDRESS>
05:48:35.564 [main] INFO  i.netty.resolver.dns.DnsNameResolver - msn.com: <IP_ADDRESS>
05:48:35.564 [main] INFO  i.netty.resolver.dns.DnsNameResolver - ask.com: <IP_ADDRESS>
05:48:35.564 [main] INFO  i.netty.resolver.dns.DnsNameResolver - soso.com: <IP_ADDRESS>
05:48:35.564 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.com.br: <IP_ADDRESS>
05:48:35.564 [main] INFO  i.netty.resolver.dns.DnsNameResolver - tumblr.com: <IP_ADDRESS>
05:48:35.564 [main] INFO  i.netty.resolver.dns.DnsNameResolver - paypal.com: <IP_ADDRESS>
05:48:35.565 [main] INFO  i.netty.resolver.dns.DnsNameResolver - mail.ru: <IP_ADDRESS>
05:48:35.565 [main] INFO  i.netty.resolver.dns.DnsNameResolver - xvideos.com: <IP_ADDRESS>
05:48:35.565 [main] INFO  i.netty.resolver.dns.DnsNameResolver - microsoft.com: <IP_ADDRESS>
05:48:35.565 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.ru: <IP_ADDRESS>
05:48:35.565 [main] INFO  i.netty.resolver.dns.DnsNameResolver - reddit.com: <IP_ADDRESS>
05:48:35.565 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.it: <IP_ADDRESS>
05:48:35.565 [main] INFO  i.netty.resolver.dns.DnsNameResolver - imgur.com: <IP_ADDRESS>
05:48:35.565 [main] INFO  i.netty.resolver.dns.DnsNameResolver - 163.com: <IP_ADDRESS>
05:48:35.565 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.es: <IP_ADDRESS>
05:48:35.566 [main] INFO  i.netty.resolver.dns.DnsNameResolver - imdb.com: <IP_ADDRESS>
05:48:35.566 [main] INFO  i.netty.resolver.dns.DnsNameResolver - aliexpress.com: <IP_ADDRESS>
05:48:35.566 [main] INFO  i.netty.resolver.dns.DnsNameResolver - t.co: <IP_ADDRESS>
05:48:35.566 [main] INFO  i.netty.resolver.dns.DnsNameResolver - go.com: <IP_ADDRESS>
05:48:35.566 [main] INFO  i.netty.resolver.dns.DnsNameResolver - adcash.com: <IP_ADDRESS>
05:48:35.566 [main] INFO  i.netty.resolver.dns.DnsNameResolver - craigslist.org: <IP_ADDRESS>
05:48:35.567 [main] INFO  i.netty.resolver.dns.DnsNameResolver - amazon.co.jp: <IP_ADDRESS>
05:48:35.567 [main] INFO  i.netty.resolver.dns.DnsNameResolver - alibaba.com: <IP_ADDRESS>
05:48:35.567 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.com.mx: <IP_ADDRESS>
05:48:35.567 [main] INFO  i.netty.resolver.dns.DnsNameResolver - stackoverflow.com: <IP_ADDRESS>
05:48:35.568 [main] INFO  i.netty.resolver.dns.DnsNameResolver - xhamster.com: <IP_ADDRESS>
05:48:35.568 [main] INFO  i.netty.resolver.dns.DnsNameResolver - fc2.com: <IP_ADDRESS>
05:48:35.568 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.ca: <IP_ADDRESS>
05:48:35.568 [main] INFO  i.netty.resolver.dns.DnsNameResolver - bbc.co.uk: <IP_ADDRESS>
05:48:35.568 [main] INFO  i.netty.resolver.dns.DnsNameResolver - espn.go.com: <IP_ADDRESS>
05:48:35.568 [main] INFO  i.netty.resolver.dns.DnsNameResolver - cnn.com: <IP_ADDRESS>
05:48:35.568 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.co.id: <IP_ADDRESS>
05:48:35.569 [main] INFO  i.netty.resolver.dns.DnsNameResolver - people.com.cn: <IP_ADDRESS>
05:48:35.569 [main] INFO  i.netty.resolver.dns.DnsNameResolver - gmw.cn: <IP_ADDRESS>
05:48:35.569 [main] INFO  i.netty.resolver.dns.DnsNameResolver - pornhub.com: <IP_ADDRESS>
05:48:35.569 [main] INFO  i.netty.resolver.dns.DnsNameResolver - blogger.com: <IP_ADDRESS>
05:48:35.569 [main] INFO  i.netty.resolver.dns.DnsNameResolver - huffingtonpost.com: <IP_ADDRESS>
05:48:35.569 [main] INFO  i.netty.resolver.dns.DnsNameResolver - flipkart.com: <IP_ADDRESS>
05:48:35.569 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.com.tr: <IP_ADDRESS>
05:48:35.569 [main] INFO  i.netty.resolver.dns.DnsNameResolver - amazon.de: <IP_ADDRESS>
05:48:35.569 [main] INFO  i.netty.resolver.dns.DnsNameResolver - netflix.com: <IP_ADDRESS>
05:48:35.569 [main] INFO  i.netty.resolver.dns.DnsNameResolver - onclickads.net: <IP_ADDRESS>
05:48:35.569 [main] INFO  i.netty.resolver.dns.DnsNameResolver - kickass.to: <IP_ADDRESS>
05:48:35.569 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.com.au: <IP_ADDRESS>
05:48:35.569 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.pl: <IP_ADDRESS>
05:48:35.570 [main] INFO  i.netty.resolver.dns.DnsNameResolver - xinhuanet.com: <IP_ADDRESS>
05:48:35.570 [main] INFO  i.netty.resolver.dns.DnsNameResolver - ebay.de: <IP_ADDRESS>
05:48:35.570 [main] INFO  i.netty.resolver.dns.DnsNameResolver - wordpress.org: <IP_ADDRESS>
05:48:35.570 [main] INFO  i.netty.resolver.dns.DnsNameResolver - odnoklassniki.ru: <IP_ADDRESS>
05:48:35.570 [main] INFO  i.netty.resolver.dns.DnsNameResolver - google.com.hk: <IP_ADDRESS>
05:48:35.570 [main] INFO  i.netty.resolver.dns.DnsNameResolver - adobe.com: <IP_ADDRESS>
05:48:35.570 [main] INFO  i.netty.resolver.dns.DnsNameResolver - dailymotion.com: <IP_ADDRESS>
05:48:35.570 [main] INFO  i.netty.resolver.dns.DnsNameResolver - dailymail.co.uk: <IP_ADDRESS>
05:48:35.570 [main] INFO  i.netty.resolver.dns.DnsNameResolver - indiatimes.com: <IP_ADDRESS>
05:48:35.570 [main] INFO  i.netty.resolver.dns.DnsNameResolver - thepiratebay.se: <IP_ADDRESS>
05:48:35.570 [main] INFO  i.netty.resolver.dns.DnsNameResolver - amazon.co.uk: <IP_ADDRESS>
05:48:35.570 [main] INFO  i.netty.resolver.dns.DnsNameResolver - xnxx.com: <IP_ADDRESS>
05:48:35.570 [main] INFO  i.netty.resolver.dns.DnsNameResolver - rakuten.co.jp: <IP_ADDRESS>
05:48:35.571 [main] INFO  i.netty.resolver.dns.DnsNameResolver - dropbox.com: <IP_ADDRESS>
05:48:35.571 [main] INFO  i.netty.resolver.dns.DnsNameResolver - tudou.com: <IP_ADDRESS>
05:48:35.571 [main] INFO  i.netty.resolver.dns.DnsNameResolver - about.com: <IP_ADDRESS>
05:48:35.571 [main] INFO  i.netty.resolver.dns.DnsNameResolver - cnet.com: <IP_ADDRESS>
05:48:35.571 [main] INFO  i.netty.resolver.dns.DnsNameResolver - vimeo.com: <IP_ADDRESS>
05:48:35.571 [main] INFO  i.netty.resolver.dns.DnsNameResolver - redtube.com: <IP_ADDRESS>
05:48:35.571 [main] INFO  i.netty.resolver.dns.DnsNameResolver - blogspot.in: <IP_ADDRESS>

Should be fixed by @normanmaurer 's recent work.


Migration error with default double value

When you have a double property that has a default double value, then ef database update command throws
Cannot set default value '0' of type 'System.Int32' on property 'XXX' of type 'System.Double' in entity type 'YYY'.
Fluent configuration:
mb.Property(p => p.Uptime).HasDefaultValue<double>(0.0).IsRequired();
Created migration file:
migrationBuilder.AlterColumn<double>(
    name: "Uptime",
    table: "ServersStatusRate",
    nullable: false,
    defaultValue: 0);

Snapshot file:
b.Property<double>("Uptime")
     .ValueGeneratedOnAdd()
     .HasDefaultValue(0);

Are you on RC2?

Yes. It is RC2 project.
On RC1 it worked correctly.

Seeing this as well with shorts
Cannot set default value '10' of type 'System.Int32' on property 'SortOrder' of type 'System.Int16' in entity type 'CurriculumMapItem'
but I can fix with doing an explicit cast
entity.Property(e => e.SortOrder).HasDefaultValue((short)10);

@geoffmmorgan The behavior you are seeing is by design, we currently don't perform value conversion in this code, even if it's safe


Chime Audio Control MinimumValue <-> SystemAudioVolume Check

https://dortania.github.io/OpenCore-Post-Install/cosmetic/gui.html
In the post install, play audio chime section for MacOS, Hackintosh

What do you think about adding some kinda informational text next to the "UEFI->Audio->MinimumVolume" that shows the value of SystemAudioVolume. Or maybe a warning when the value of "UEFI->Audio->MinimumVolume" is lower than the "NVRAM->SystemAudioVolume"

I am on Version 20220043 now I can see you've added it.
Done & dusted!
Dude, you are amazing!


Consistent article width across breakpoint

@mcrascal this is the thing I was mentioning yesterday
Situtation today:

Weird "getting larger as you make width smaller" effect. Toggles between 70ch and 80ch width
Especially odd when there is no Table of Contents

Proposed Change

Always 70ch width

Thoughts?

Including going across mobile breakpoint


Container with most water.java

Description
Added the solution to 'Container with most water' problem in Java in Leetcode folder.
Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[yes] My code follows the style guidelines(Clean Code) of this project
[yes] I have performed a self-review of my own code
[yes] I have commented my code, particularly in hard-to-understand areas
[yes] I have created a helpful and easy to understand README.md
[yes] I have made corresponding changes to the documentation
[yes] My changes generate no new warnings
[yes] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

DS ALGO PROJECTS ARE NOT COUNTED FOR HACKTOBERFEST21 so i will close this PR


[RigidSpaces] Make initial definitions and state lemmas

Added some thoughts about rigid spaces.
Feel free to decline if you feel it isn't "on topic" for this repo, but perhaps it could be another fun formalization puzzle.

Yeah, maybe if this is an open-ended formalization rather than a closed-off puzzle then maybe this is not the right repo for it.


Add graphFetch cross key cache tests

Hi @pierredebelen, I added the test in legend-engine-executionPlan-execution-store-relational module which does not have access to parser and plan generator. Should I move it to the server module (doesn't seem to be the correct place)?

As much as we can't have dependency to the parser & compiler in Execution's runtime & compile scope, I think it's ok to have dependencies to (legend-engine-language-pure-*) in the test scope as it will make the tests far more readable. I did the same in legend-engine-test-runner-mapping

Added the tests in ASCII


Transaction should be FnOnce not Fn

This allows move operations

Resolved in https://github.com/stepfunc/scursor/commit/6d498abc47bac5ab6a767e0d9bd282dd01bedc84


Please share the code to load the raw dataset.

Hi @vickypar @syfantid @kcristinaa, thank you for your interesting GitHub repository. I want to replicate your code with all four original datasets you mentioned, but I seem to need help from the beginning.
Could you please share your code to load the raw dataset, such as SWELL?
I think that the Initial_Analysis-checkpoint.ipynb from .ipynb_checkpoints is empty. The file swell_new.csv only has 3141 rows, which is much fewer records than the original SWELL dataset (I think).
Please forgive if I misunderstand anything.
Thank you very much,
Regards,
Hieu

Hi @hieutv85. The code to load the raw datasets is located under "Data Formatting" folder. As for the SWELL-KW dataset, we used only the physiological features of the dataset to be comparable to the other datasets, this is why it contains only 3141 rows.

Hi Hieu,
Thank you for your e-mail.
The code to load the raw datasets is located under "Data Formatting" folder. As for the SWELL-KW dataset, we used only the physiological features of the dataset to be comparable to the other datasets, this is why it contains only 3141 rows.
Best regards,
Vicky

Από: Hieu Vu Tran @.>
Στάλθηκε: Τετάρτη, 13 Μαρτίου 2024 3:43 πμ
Προς: vickypar/personalized.ml.for.stress.detection @.>
Κοιν.: Subscribed @.***>
Θέμα: [vickypar/personalized.ml.for.stress.detection] Please share the code to load the raw dataset. (Issue #1)
Hi, thank you for your interesting GitHub repository. I want to replicate your code with all four original datasets you mentioned, but I seem to need help from the beginning.
Could you please share your code to load the raw dataset, such as SWELL?
I think that the Initial_Analysis-checkpoint.ipynbhttps://github.com/vickypar/personalized.ml.for.stress.detection/blob/main/.ipynb_checkpoints/Initial_Analysis-checkpoint.ipynb from .ipynb_checkpoints is empty. The file swell_new.csv only has 3141 rows, which is much fewer records than the original SWELL dataset (I think).
Please forgive if I misunderstand anything.
Thank you very much,
Regards,
Hieu
—
Reply to this email directly, view it on GitHubhttps://github.com/vickypar/personalized.ml.for.stress.detection/issues/1, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AWZIUHZCUBPGLMIAAEENX7DYX6VKXAVCNFSM6AAAAABETIMDK6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGE4DEOJVGUZDQMY.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Hi @vickypar, thank you very much for your support.


Testing

Adding two tests to helm

forseti inventory list
forseti model list

These can be invoked by helm test forseti
Please do not merge before #19

/gcbrun

/gcbrun

/gcbrun


add Screens system

Adds "show", "hide", "at" and "with" keywords to RKScript and Screen nodes.
This implements #143

Hello :)
I will not review 2761 files with +91,863 −31 updates.
Please say me the files you want I see, or merge it if you are confident :)

Hello :)
I will not review 2761 files with +91,863 −31 updates.
Please say me the files you want I see, or merge it if you are confident :)

This is not ready for review/merge as it doesn't work as it should.
The biggest problem I have is that I have on helper object BaseScreen.gd,
so I can easy you the same code for Node2D as for Control.
But for some reason it works for Node2D, but not for Control.
See scripts: Screen.gd and Screen2D.gd
Screens are added to Rakugo Scripting by Screens.gd singleton.
There is res://game/ScreensExample.tscn scene that I use for testing Screens visually.

We no longer work on 1.0


fetchgithub: support for sparse checkouts

Motivation for this change
If we one day try to use some openbsd utilities as asked here https://github.com/NixOS/nixpkgs/issues/113483, we
will have either to build the entire openbsd project in a single derivation (not optimal) or to take only a few projects inside it and build them on their own.
This PR adds a feature to fetchFromGitHub to sparseCheckout a repo. This is for example what you would use to only extract openbsd's make implementation.
src = fetchFromGitHub {
  owner = "openbsd";
  repo = "src";
  rev = "e5d32326ca316ca97670d484b46db42e9d6da269";
  sparseCheckout = "usr.bin/make";
  sha256 = "12jicmj3liicp2j02jz0i4yan81m3i7w0gbfrqhm9bcckfhdh7jl";
};

This optimization reduces the band width usage which is already quite big when working on nixpkgs.

The implementation behind this feature uses github's svn bridge which seems to be the only way to fetch a github repo's sub/subdir from a specific commit.
Warning

We can't use the print_results mechanism that shows informations about the git fetch such has the full rev as it's obviously not compatible with svn. This could be fixed with a svn version though.
It should work with tags but other than that and commit shas, I might have missed some edge cases.

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 113689 at e4a82e37 run on aarch64-linux 1

11 packages built:

bundix
cabal2nix
crate2nix
dep2nix
go2nix
haskellPackages.update-nix-fetchgit
nix-prefetch-git
nix-prefetch-scripts
nix-update-source
update-nix-fetchgit
vgo2nix

@SCOTT-HAMILTON What about:
git clone --filter=tree:0 --no-checkout --depth=1 https://github.com/openbsd/src.git
cd src/
git sparse-checkout init --cone
git sparse-checkout set usr.bin/make
git fetch --depth=1 origin e5d32326ca316ca97670d484b46db42e9d6da269
git checkout e5d32326ca316ca97670d484b46db42e9d6da269

This is good but it still fetches all the commits.

I'd rather support git sparse-checkout in fetchgit, be it slower or not, than further increase the complexety of fetchFromGitHub with essentially a third way of fetching stuff from GitHub which uses a non-obvious method under non-obvious circumstances.


fix(material/autocomplete): add missing aria-label for autocomplete panel

Fixes https://github.com/angular/components/issues/20888

Change implementation to take aria-label input or set aria-labelledby to trigger form field id.
Reflect changes in MDC
Add unit tests

Addressed comments.

I think the CI failure is a previous commit message error


Proper convolution mode for fast GPU processing

Default convolution mode is very slow, as a result sherpa-onnx-gpu is much slower than CPU. With this fix the decoding speed is ok.
See also
https://github.com/microsoft/onnxruntime/issues/12880#issuecomment-1330442188
https://onnxruntime.ai/docs/execution-providers/CUDA-ExecutionProvider.html#cudnn_conv_algo_search

Thank you for your first contribution!


Update redhat-rhui.md

add regions names for rhui3 IPs and separate and capitalize region names on rhui 4 for readability.

https://csstoolkit.azurewebsites.net/(S(t02gve1ogjzbf1uuvsvnpjfu))/Home/MicrosoftIPs

@MicrosoftAzureAaron - when you get a chance, please respond to the instructions in this comment: https://github.com/MicrosoftDocs/azure-docs/pull/114247#issuecomment-1703310423
@mamccrea - after the CLA is signed by @MicrosoftAzureAaron :

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#assign: @mamccrea
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@microsoft-github-policy-service agree
From: microsoft-github-policy-service[bot] @.>
Sent: Friday, September 1, 2023 14:58
To: MicrosoftDocs/azure-docs @.>
Cc: Aaron Sanders @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Update redhat-rhui.md (PR #114247)
@MicrosoftAzureAaronhttps://github.com/MicrosoftAzureAaron please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term "You" includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement
Contribution License Agreement
This Contribution License Agreement ("Agreement") is agreed to by the party signing below ("You"),
and conveys certain license rights to Microsoft Corporation and its affiliates ("Microsoft") for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

Definitions.
"Code" means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
"Project" means any of the projects owned or managed by Microsoft and offered under a license
approved by the Open Source Initiative (www.opensource.orghttp://www.opensource.org/).
"Submit" is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as "Not a Submission."
"Submission" means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.
Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.
Originality of Work. You represent that each of Your Submissions is entirely Your original work.
Should You wish to Submit materials that are not Your original work, You may Submit them separately
to the Project if You (a) retain all copyright and license information that was in the materials as You
received them, (b) in the description accompanying Your Submission, include the phrase "Submission
containing materials of a third party:" followed by the names of the third party and any licenses or other
restrictions of which You are aware, and (c) follow any other instructions in the Project's written
guidelines concerning Submissions.
Your Employer. References to "employer" in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term "You" in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.
Licenses.

Copyright License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
parties.
Patent License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.
Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.

Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
You later become aware that would make Your representations in this Agreement inaccurate in any
respect.
Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.
Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/114247#issuecomment-1703258533, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5CCDPFB2ICMCSWKFMFECLTXYI45TANCNFSM6AAAAAA4H77ZXI.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@mamccrea - can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
Thanks, PR review team

@mamccrea,
Can you review this old PR and determine whether it needs to be closed or merged?

Teams message to mamccrea

author investigating (per Teams msg)

This PR is way too old and conflicts with updates recently made, I will update the current page with the proposed changes.

Thanks @esvmicrosoft - #please-close


Add support for blogs with > 500 posts.

This just puts the existing code in a loop and made multiple max-sized calls to the gdata API, with some tracking state to make sure all the posts get pulled.

Awesome, thanks a lot Anna.


APP-394: [Objective-C] Update all sample applications projects.

http://jira.kaaproject.org/browse/APP-394

@kaa-leeroy test this fully please

@kaa-leeroy test this fully please

@kaa-leeroy test this fully please


Tabular: Fixed TextPrediction crash when NaN values are present.

Issue #, if available:
Description of changes:

Fixes crash if numeric columns have NaN values in TextPrediction.

TODO:

[ ] Improve imputation method. Currently defaults to -1, which is not ideal.
[ ] Fix categorical features: Currently not used by TextPrediction model.
[ ] Fix categorical features with NaN values at test time. Currently causes crashes.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-852-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-852/1/index.html

Job PR-852-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-852/1/index.html


added validating designs

Notes for Reviewers
This PR fixes #346
Signed commits

[x] Yes, I signed my commits.

Thank you @hargunkaur286. LGTM 🚀

@hargunkaur286  a conflict to address here...

merge conflict


Branchv1.4 dev guide3

closes #308

Codecov Report

Merging #333 (61feed0) into master (c6dcc3e) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #333   +/-   ##
=========================================
  Coverage     66.04%   66.04%
  Complexity      889      889
=========================================
  Files           139      139
  Lines          3222     3222
  Branches        543      543
=========================================
  Hits           2128     2128
  Misses          980      980
  Partials        114      114

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c6dcc3e...61feed0. Read the comment docs.


check if image file exists

If you try to embed an image which doesn't exist the email isn't valid and won't be delivered without any error message.
I refactored the code a little bit as the embedImages method got a bit large and hard to read with all the things going on, i hope that's ok with you.

I guess you're right. Probably also makes problems with multiple redirects. Maybe the best is to just ignore redirects and only evaluate the first response.

Ran into some other problems with more testing as the http version could be different as well. with getimagesize it also seems to work with redirects etc. so this to be a good solution.

Viele Danke
I will release a new version with your fix.


IONIC 5 with Capacitor facing to launch another app and get callback using startActivityForResult

I am using Ionic Angular with capacitor, we need to launch an external application which is our dependent application (Nativescript). With the ID of the app I need to launch and get callback once get image data. How to achieve this using Intent?
Getting error block log in console
`  const options = {
action: this.webIntent.ACTION_GET_CONTENT,
package: 'de.myapp.eco'  /*App package id in store installed in device */
}
this.webIntent.startActivityForResult(options).then((onSuccess) => {
  console.log('onSuccess',onSuccess)
}).catch((error: any) => console.log('error',error));`

Can you please guide me out to achieve the result?
@darryncampbell  @mcelotti @mattdsteele

To invoke another application directly you can specify the component, please see https://github.com/darryncampbell/plugin-intent-api-exerciser/blob/master/www/js/index.js#L233 for an example

Yes @darryncampbell for example 'A' app calls 'B' app, In this cased 'B' is opened but 'A' is closed. What I want is that 'A' app should be opened after B is closed. Hope you got it? How to achieve this using startActivityForResult?

How to achieve this using startActivityForResult?

For StartActivityForResult example see https://github.com/darryncampbell/plugin-intent-api-exerciser/blob/master/www/js/index.js#L190.  To return data from StartActivityForResult see https://github.com/darryncampbell/plugin-intent-api-exerciser/blob/master/www/js/index.js#L347 (this is test code to return from being invoked by https://github.com/darryncampbell/plugin-intent-api-exerciser-helper/blob/master/app/src/main/java/com/darryncampbell/pluginintentapiexerciserhelper/MainActivity.java#L24)


CI: Migrate ROCm build test from FlexCI to GitHub Actions

ROCm build test does not require GPU, so let's run on GitHub Actions.

Let's use #6034 instead!


ros2 version demo, how to set the config/params.yaml file and which bag to use?

Hi:
I am trying to run the ros2 versin of lio-sam, could someone tells how to set the config/params.yaml file and which bag to use?
Thanks a lot

Hi,
despite minor differences in syntax, configuration shall be similar to the ros1 version, so please follow the recommendations in README.md. You can even use the bags provided for ros1 and bridge to ros2 using https://github.com/ros2/ros1_bridge.

Hi, thanks for  the replay. Which bag should I use for the default parameters in branch ros2?

I'm not aware of a dataset that fits the current default parameters. They fit my rosbags, but unfortunately I'm not allowed to publish them for privacy reasons. I therefore suggest to start with the Rooftop Dataset (see README.md) and configure params.yaml as it was before this commit was merged into master: https://github.com/TixiaoShan/LIO-SAM/commit/df05f8a26e52c70240a809837a848ddfee2cfcfb (This commit was not yet merged to ros2 branch).

Get it. I will try then. Thanks a lot.


[FLINK-7047] [travis] Reorganize build profiles

Builds on-top of #4226 and #4227.
This PR reorganizes the test groups.

core - executes tests for core, runtime, streaming-java, scala, etc
libraries - executes tests for modules libraries and storm
connectors - executes tests for connectors and wikiedits
tests - executes tests for flink-tests and examples
misc - executes tests for yarn, mesos, fs-tests, dist

The main change (and worst part) is that every module (or their respective parent) now have a run-tests profile that is activated when the specific property for that groups was set.
For example, tests for flink-libraries are activated if the flink.test.lib property is set.
For this to work it was necessary to disable the test execution by default. Execution of tests is now strictly opt-in for each module (or their parent).
To keep the number of build profiles <= 10 I've also reduced the combinations of jdk+scala+hadoop that we're testing to 2:

oraclejdk8 + scala11 + hadoop2.8.0
openjdk7 + scala10 + hadoop2.4.1

For the jdk7 profile max build times hover around 45 minutes for the core tests; for jdk8 the same build takes 40 minutes.
I tried to reduce this further my cutting out parts of the compilation, specifically the scala modules which easily add 6-8 minutes, but i couldn't find a way that properly works and is maintainable enough. Instead of fiddling with maven it's probably easier just to split the entire repo and call it a day.

@zentol could you start a mailing list discussion and describe your preference for splitting the tests in this manner or splitting the repo? Despite heroic efforts by you and Robert keeping the test times under the timeout continues to be a Sisyphean task. The number of tests never truly drops so the test times will only decrease on the off chance that TravisCI bumps the number of cores (or Google increases CPU performance, which they have never done).

I would merge this PR in any case. It's a nice short-term option that is more stable than the previous approach; regardless of how many times we add in flink-runtime we can still test connectors/libs and vice versa.

Note that we can further reduce the build-time of the core profile to ~35 minutes by skipping the compilation libraries/connectors. At least we should, if it weren't for flink-7070...

I've moved a few more modules into the misc. group:

flink-metrics
flink-java8
flink-streaming-contrib
flink-scala-shell

For the core group we now only compile modules that the core modules actually depend on, reducing the core build time to 30 minutes: https://travis-ci.org/zentol/flink/builds/249710980

So executing mvn clean verify won't run the tests, right?
Have you considered doing this, basically without touching the pom files at all?
Basically by having a script that says
"cd flink-core; mvn install
cd flink-runtime; mvn install
cd flink-tests; mvn verify
"
I think there's also a command to tell maven "build all your dependencies"

I think we should be able to do this as a two-step process without changing the poms:
mvn install -pl flink-tests,flink-foo-bar -am -DskipTests -Dmaven.javadoc.skip=true
mvn verify -pl flink-tests,flink-foo-bar -Dmaven.javadoc.skip=true

The first line will make sure that we have all the dependencies built, the second one only executes the tests in the given submodules. We cannot do it as one step because running mvn verify -pl flink-tests,... -am would run the tests also on all dependencies of flink-test,....
However, it seems we can't do this because the second incantation fails with
[WARNING] Some problems were encountered while building the effective model for org.apache.flink:flink-scala-shell_2.11:jar:1.4-SNAPSHOT
[WARNING] 'artifactId' contains an expression but should be a constant. @ org.apache.flink:flink-scala-shell_${scala.binary.version}:[unknown-version], /Users/aljoscha/Dev/flink/flink-scala-shell/pom.xml, line 30, column 14

that is including the Scala version in our artifact IDs broke this.

There's also this interesting approach which limits changes to the root POM: https://stackoverflow.com/a/39562385/4770039

@aljoscha this may be caused by publishing pom's with unresolved ${scala.binary.version}. I am planning to file a ticket after #4221 is merged. The StackOverflow link looks promising.

mvn verify should run all tests since the default for all added properties is true. But yes, it currently doesn't. I don't quite understand this as the default for all groups is true (i.e. all test profiles should activate) and I'm not modifying the phases of these profiles.
Maven's -am and -amd options don't work for us since these don't build dependencies marked as provided, i.e. most core flink dependencies. You can easily verify this yourself.
Maven's -pl command is a bit brittle in general as we have to include every single module; we can't just point to flink-libraries and call it a day. This adds a maintainability problem; a new module will not be tested on travis if the contributor/reviewer isn't aware of the magic in the travis scripts. This is less likely with the approach in this PR as part of the magic is in the poms which are more likely to be seen by a developer.

corrected my previous comment regarding the problems of -am and -amd.

another more sane option would be to add a new module for each group that has a dependency for each module we want tested. THEN we could use the -am option.

WIth the existing surefire configuration we also cannot do this in 2 steps, one for compilation and one for tests. It is not possible to only run tests with any maven invocation that includes a life-cycle (i.e verify), which means that you have to recompile some modules twice which isn't an option because scala compilation is so utterly horrible.
You could theoretically cd into each project after compilation and directly invoke the surefire plugin, but this doesn't work as we have 2 executions (1 for unit tests, 1 for IT cases), and when invoking a plugin directly you can at most run 1 execution and it has to be named either "default-test" or "default-cli". This would be possible in maven 3.3.1, but we can't use that without messing with the shading, We could use maven 3.3.X if we split the repo and add a separate one for flink-dist, but that's not gonna happen anytime soon.
We could directly invoke the surefire plugin if we merged our surefire executions, but then we're still left with the problem of having to keep the travis scripts in sync with the directory structure of the project.

@rmetzger Now i understand why the tests aren't run. I thought that I was activating the profiles with the properties in the root pom.xml, but this isn't the case. I was just setting the system properties in the travis scripts...
back to the drawing board i guess...

@rmetzger I can fix the issue with verify by reverting the profile logic. Instead of activating the surefire plugin in each module, the plugin is enabled by default in the root pom but disabled in the profile of each module if the property is set

mvn verify now works as it should, execution tests and stuff.

Currently experimenting with specifying every module to test using the -pl option.

We can do this in a more centralized way using the -pl option as @aljoscha suggested (see https://github.com/zentol/flink/tree/7047_alt2), but this is blocked by FLINK-7112 & FLINK-7112.
https://travis-ci.org/zentol/flink/builds/250679622

@aljoscha @rmetzger I've reworked this PR, could you take another look?

This looks nice now! Is there verification, though, that we didn't forget any modules in the list of tested modules?

There's no verification, and i don't think that this is a blocking issue. We can verify it now manually and open an issue to add some magic later on.

I've got an idea on how to make sure that all modules are guaranteed to be covered, sit tight...

I've reworked the "misc" group. There is no longer a dedicated list of modules for this group, but instead we test all modules that aren't included in any other group.
All other groups have a comma-separated list of modules to test, like flink-runtime,flink-core. For the "Misc" group we concatenate those lists and negate them, like !flink-runtime,!flink-core. What's left is the modules that aren't contained in another group, which means all new modules would be run automatically.
The compilation step of this group simply builds flink completely; this was basically required anyway since the group contained flink-dist.

+1; total run time has dropped by almost half

I would hope so, because the number of version combinations we check is also halved. 😉

@aljoscha true. Now that proportionally more time is spent compiling we may be able to enable parallel builds for the compilation phase. I think most issues were with running tests where dependencies were not properly configured.

yes we could build with parallel builds, although i encountered the storm module acting up once.
It also, at least in early prototypes, didn't provide a big improvement. (iirc 1 minute when building Flink completely) The results may be different now.
That said, I would defer further tinkering on small details to follow-ups, since local builds are still timing out and I don't want to delay this further unless something is actually broken.

I think this looks good.
It's basically a change now restricted to the build system only.
+1 to give it a try on master and see how things go with it.

merging.


Default Content Width and Height

Hello,
Thank you for this awesome component!
I'm wondering in case we have the following situation:
<ContentGroup title="About">
    Link C
    Link D
</ContentGroup>

See example here:
https://codesandbox.io/s/rlz4q3x2zp
Shouldn't this situation by default get the defaultContentWidth and defaultContentHeight?
I wanted to open a PR for this but I noticed that you have a comment saying:
// if width and height are not specified, that means we don't want to render the content group i.e. we only
// want to render root item

So I'm not sure what this is intended to do. What do you mean by root item?
  memoizeMenuData = memoize((columnWidth, children) => React.Children.map(children, (child, i) => {
    // if width and height are not specified, that means we don't want to render the content group i.e. we only
    // want to render root item
    const {width, height} = child.props;
    let sanitisedWidth, sanitisedHeight;

    if (!width && !height) {
      sanitisedWidth = 0;
      sanitisedHeight = 0;
    } else {
      // if width or height is not specified, add defaults
      sanitisedWidth = width || defaultContentWidth;
      sanitisedHeight = height || defaultContentHeight;
    }

Also is it possible to have a link without a ContentGroup?
 <SiteNav>
    I'm a link without a ContentGroup
    <ContentGroup title="About">
      Link B
      Link C
    </ContentGroup>
    <ContentGroup title="Contact" width="420" height="270">
      Link D
      Link E
    </ContentGroup>
  </SiteNav>

Thanks!

@miukimiu hi there, I've updated the code recently and I didn't update the readme so apologies.
A root item is the grid item representing the "title" prop of a ContentGroup. See the screenshot below.

To have a link root item without a content group, you can do this:
<ContentGroup title="Some Link" rootUrl="https://to/somewhere" />

That's the reason why a content group width and height is set to 0 if both are unspecified. The site nav assumes you don't want a content group. Check my blog for a demo of a link without a content group.
I'll update the documentation to reflect this information. Let me know if this works!

Yes, it works! Thank you!! 😄


Update description of Provider SDK

I think "Go Provider for Pulumi" as a noun phrase reminds me a lot of say, "AWS Provider for Pulumi". This SDK is for building providers for Pulumi in Go, rather than a "Go Provider".

We might want to consider a name change before 1.0.0.