--- Day changed Wed Jun 20 2018 00:07 -!- tiagotrs [~user@p5DDB62C8.dip0.t-ipconnect.de] has joined #c-lightning 00:07 -!- tiagotrs [~user@p5DDB62C8.dip0.t-ipconnect.de] has quit [Changing host] 00:07 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 00:07 < rusty> sturles: ... 0bin again? 00:08 -!- kabaum [~kabaum@2.65.45.160.mobile.tre.se] has joined #c-lightning 00:18 -!- kabaum [~kabaum@2.65.45.160.mobile.tre.se] has quit [Ping timeout: 255 seconds] 00:21 < sturles> https://0bin.net/paste/vNYVmpwfsqX+V7FH#1z4WXIVRbUQ-SkfijfXFuJxM3Vt1iOshfd7uEsf03yz 00:24 < rusty> sturles: wow, you're talented :) Let me look harder... 00:28 < rusty> sturles: OK, all I can think of is that lseed.bitcoinstats.com has a bug? I mean, unless you're doing something really weird at your end. I've pinged cdecker on that, and assigned him to it... 00:28 < rusty> sturles: you can comment out the test, it's OK anyway... 00:40 -!- kabaum [~kabaum@94.234.33.230] has joined #c-lightning 00:47 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning 00:49 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 276 seconds] 00:57 < sturles> Testing again with 8.8.8.8 as nameserver. 00:58 < sturles> (My current nameserver does not hijack NXDOMAIN responses.) 01:04 < sturles> Same result. 01:38 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 01:39 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 01:44 -!- kabaum [~kabaum@94.234.33.230] has quit [Read error: Connection reset by peer] 02:13 < windsok> thanks rusty. current server is going to be trashed, so sounds like I should be OK just to copy the whole .lightning directory over to new server 02:33 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 02:37 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 265 seconds] 03:07 < sturles> Made test_connect return at once so it could test further. Got to test_gossip_weirdalias: 03:08 < sturles> https://0bin.net/paste/BrXJ5XCkh0Vd+Yt-#oKF8K9l2MYlzOObabbbD7y25W57Npmw9xKTWFAvBZk1 04:10 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 256 seconds] 04:12 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 240 seconds] 04:32 -!- deusexbeer [~deusexbee@095-129-175-233-dynamic-pool-adsl.wbt.ru] has joined #c-lightning 04:35 -!- kabaum [~kabaum@2.67.236.210.mobile.tre.se] has joined #c-lightning 04:43 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 04:46 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 05:27 -!- kabaum [~kabaum@2.67.236.210.mobile.tre.se] has quit [Ping timeout: 268 seconds] 05:37 -!- kabaum [~kabaum@94.234.38.89] has joined #c-lightning 06:09 -githubby:#c-lightning- [lightning] cdecker opened pull request #1601: Add cli option to disable DNS node ID lookup (master...disable-dns) https://git.io/fG2yj 06:09 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 256 seconds] 06:27 < bitonic-cjp> Is it normal for Valgrind to go beserk on the Python 3 interpreter? 06:30 < bitonic-cjp> I got lightningd to fork and run a tiny Python script, and now Valgrind complains about jumps depending on uninitialized values, with lots of Python mentions in its report. 06:31 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 06:35 < bitonic-cjp> hmm, apparently it is; Python is doing weird things with memory management that confuse Valgrind. :-( 07:11 -githubby:#c-lightning- [lightning] jb55 opened pull request #1602: gossipd: fix compile error, uninitialized variable (master...gcc-compile-err) https://git.io/fZuMK 07:27 -!- daouzo23 [~daouzo23@178.165.128.81.wireless.dyn.drei.com] has joined #c-lightning 07:37 -!- j9m [~j9m@47.157.125.55] has quit [Remote host closed the connection] 07:40 -!- daouzo23 [~daouzo23@178.165.128.81.wireless.dyn.drei.com] has quit [Ping timeout: 276 seconds] 07:48 -!- daouzo23 [~daouzo23@178.165.128.81.wireless.dyn.drei.com] has joined #c-lightning 08:34 -!- Xian001 [~xian001@47.184.129.94] has joined #c-lightning 08:38 -!- grafcaps [~haroldbr@107.147.175.194] has joined #c-lightning 08:43 -!- grafcaps [~haroldbr@107.147.175.194] has quit [Ping timeout: 256 seconds] 08:46 -!- daouzo23 [~daouzo23@178.165.128.81.wireless.dyn.drei.com] has quit [Ping timeout: 256 seconds] 08:52 -!- daouzo23 [~daouzo23@178.165.128.81.wireless.dyn.drei.com] has joined #c-lightning 09:02 -!- daouzo23 [~daouzo23@178.165.128.81.wireless.dyn.drei.com] has quit [Quit: Leaving] 09:03 -!- grafcaps [~haroldbr@104.137.194.255] has joined #c-lightning 09:05 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving] 09:09 < blockstream_bot> [Christian Decker, Blockstream] You can disable valgrind following the forked off process, take a look at the integration tests where we blacklist `bitcoind` for example 09:20 -!- kabaum [~kabaum@94.234.38.89] has quit [Read error: Connection reset by peer] 10:20 -!- tiagotrs [~user@p3EE2D005.dip0.t-ipconnect.de] has joined #c-lightning 10:20 -!- tiagotrs [~user@p3EE2D005.dip0.t-ipconnect.de] has quit [Changing host] 10:20 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 11:58 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 256 seconds] 12:06 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 12:36 -!- shesek [~shesek@bzq-84-110-232-144.red.bezeqint.net] has joined #c-lightning 12:36 -!- shesek [~shesek@bzq-84-110-232-144.red.bezeqint.net] has quit [Changing host] 12:36 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 13:24 -!- kabaum [~kabaum@c-5eea24ef-74736162.cust.telenor.se] has joined #c-lightning 13:34 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 14:14 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 14:25 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #1602: gossipd: fix compile error, uninitialized variable (master...gcc-compile-err) https://git.io/fZuMK 14:41 -!- grubles [~grubles@unaffiliated/grubles] has quit [Ping timeout: 256 seconds] 14:42 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning 14:46 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 255 seconds] 15:10 -!- kabaum [~kabaum@c-5eea24ef-74736162.cust.telenor.se] has quit [Ping timeout: 256 seconds] 15:35 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 248 seconds] 15:43 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 255 seconds] 16:06 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #1600: pytest: make test_connect use an unknown id. (master...make-test-connect-more-robust) https://git.io/fs3Fy 17:24 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 17:27 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 17:28 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 17:30 -!- simlay_ is now known as simlay 17:46 -!- contrapumpkin [~copumpkin@haskell/developer/copumpkin] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…] 17:54 -!- daouzo23 [~daouzo23@wl-loc177-82.liwest.at] has joined #c-lightning 18:37 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 260 seconds] 18:46 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 18:51 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 19:00 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 19:01 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 264 seconds] 19:25 -!- daouzo23 [~daouzo23@wl-loc177-82.liwest.at] has quit [Ping timeout: 276 seconds] 19:49 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 248 seconds] 19:52 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 19:55 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 20:09 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning 20:22 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 20:24 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 276 seconds] 20:42 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 21:23 -!- j9m [~j9m@47.157.125.55] has joined #c-lightning 21:28 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Ping timeout: 264 seconds] 21:40 < blockstream_bot> [Chang Li, Blockstream] can two nodes have the exactly same alias? 21:42 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 21:42 < blockstream_bot> [Chang Li, Blockstream] i currently have 2 nodes with same name but i can only find one on lnmainnet.gaben.win 21:43 < blockstream_bot> [Chang Li, Blockstream] gotta try finding the second node by id later, see if it comes up 21:43 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 21:58 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 240 seconds] 21:59 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 22:01 < molz> Chang Li, yes two nodes can have the same alias, the difference between them is their node pubkey 22:33 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #1611: Update install instructions (master...update-install-instructions) https://git.io/fCxJ7 22:45 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 23:19 -!- tiagotrs [~user@p5DDB5639.dip0.t-ipconnect.de] has joined #c-lightning 23:19 -!- tiagotrs [~user@p5DDB5639.dip0.t-ipconnect.de] has quit [Changing host] 23:19 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 23:22 < blockstream_bot> [Chang Li, Blockstream] thanks! 23:52 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 276 seconds] 23:54 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 240 seconds]