--- Day changed Tue Jun 19 2018 00:37 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Quit: Leaving] 00:48 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning 00:48 -!- ThrobbingSausage [~xian001@47.184.129.94] has joined #c-lightning 00:49 < ThrobbingSausage> Is the latest master branch effectively 0.6 ? 00:50 -!- ThrobbingSausage is now known as Xian001 01:02 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 01:03 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 01:08 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 245 seconds] 01:11 -!- StopAndDecrypt [~StopAndDe@c-73-215-253-208.hsd1.nj.comcast.net] has joined #c-lightning 01:11 -!- StopAndDecrypt [~StopAndDe@c-73-215-253-208.hsd1.nj.comcast.net] has quit [Changing host] 01:11 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning 01:19 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Remote host closed the connection] 01:19 -!- StopAndDecrypt [~StopAndDe@c-73-215-253-208.hsd1.nj.comcast.net] has joined #c-lightning 01:20 -!- StopAndDecrypt [~StopAndDe@c-73-215-253-208.hsd1.nj.comcast.net] has quit [Changing host] 01:20 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning 01:21 < sturles> What goes wrong with make check here? https://0bin.net/paste/FXlOSzOXLUAQ-9kV#wC4T3aHSOT-fPo6WCJusX6YxlzACWVnsbwxoNr0Ei4s 01:22 < sturles> test_connect FAILED for some reason. 01:51 -githubby:#c-lightning- [lightning] arowser opened pull request #1598: align generate wire template (master...align_generate_template) https://git.io/fJAj0 02:02 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 02:07 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds] 02:25 -!- kabaum [~kabaum@2.69.139.113.mobile.tre.se] has joined #c-lightning 02:29 -!- tiagotrs [~user@p5DDB5697.dip0.t-ipconnect.de] has joined #c-lightning 02:29 -!- tiagotrs [~user@p5DDB5697.dip0.t-ipconnect.de] has quit [Changing host] 02:29 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 02:40 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Remote host closed the connection] 02:59 -!- rusty [~rusty@45.124.203.40] has joined #c-lightning 02:59 -!- rusty [~rusty@45.124.203.40] has quit [Changing host] 02:59 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 03:07 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 04:00 -!- kabaum [~kabaum@2.69.139.113.mobile.tre.se] has quit [Ping timeout: 260 seconds] 04:08 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 04:31 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 05:00 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 05:30 -!- kabaum [~kabaum@94.234.33.116] has joined #c-lightning 06:01 -!- kabaum [~kabaum@94.234.33.116] has quit [Read error: Connection reset by peer] 06:13 -!- _mr_e [63e63289@gateway/web/freenode/ip.99.230.50.137] has quit [Ping timeout: 260 seconds] 06:46 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 260 seconds] 06:49 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Remote host closed the connection] 06:49 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning 07:54 < Xian001> disregard: just pulled and built latest main. "version": "v0.6rc1" 08:09 -!- _mr_e [1872418f@gateway/web/freenode/ip.24.114.65.143] has joined #c-lightning 08:09 < _mr_e> Thanks molz. So I guess the expected flow for a user trying to use a lightning service is: 08:09 < _mr_e> 1. Attempt to pay the invoice directly (If they already have at least 1 channel open elsewhere) 08:10 < _mr_e> 2. If the route can not be found, open a channel to the service 08:10 < _mr_e> 3. As more users open channels with this service, more and more users will be able to find a route without opening a new channel directly with the service 08:10 < molz> yes, exactly 08:12 < _mr_e> So let's say I open a channel with service a, and I have other users with a channel open to me... Will my channel quickly be drained by other users routing through me? 08:13 < _mr_e> and then I will not be able to send my own transaction to the service without opening a new channel? 08:14 < molz> no, when you open a channel your money is on your side, other people who have channels with you also have money on their side, right? 08:14 < _mr_e> ah right 08:15 < _mr_e> so they forward me 0.1 and i forward service a .01 and we're all good 08:15 < _mr_e> but i actually could end up receiving .01000001 08:15 < molz> and you have a direct channel to node A? 08:16 < _mr_e> right 08:16 < molz> suppose node A sells a product that you want to buy, you use your money to buy from A 08:16 < molz> then the money goes to the other side of your channel with A 08:17 < _mr_e> right 08:17 < molz> suppose someone who has a channel with you but doesn't have a channel with A, and he also wants to buy something from A 08:17 < molz> so he attemps to make a payment, and your money on the other side in channel with A is enough for this person to "borrow" 08:17 < molz> then he sends a payment to A, by sending money to you, and you send to A for him 08:18 < _mr_e> makes sense 08:19 < _mr_e> is there a way to add more funds to or increase the balance in my channel, or do I have to close 1 and open another 08:21 -!- ebx [~ebx@unaffiliated/ebex] has quit [Read error: Connection reset by peer] 08:21 < molz> not yet 08:22 < molz> there's something called "splicing" that will let us add fund to channel without having to close the channel but it's in development so i heard 08:23 < _mr_e> but during routing, someone sends me funds, which I forward to the service... effectively adds funds to my channel 08:23 < _mr_e> if I had 2 nodes, a and b 08:23 < _mr_e> b has 10 btc in a channel to a, a has 10 channels to different services 08:23 < _mr_e> can b somehow restock any of the 10 channels in a 08:24 < _mr_e> it's basically just routing, but without a forwarding 08:30 -!- tiagotrs [~user@p3EE2DE7D.dip0.t-ipconnect.de] has joined #c-lightning 08:30 -!- tiagotrs [~user@p3EE2DE7D.dip0.t-ipconnect.de] has quit [Changing host] 08:30 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 08:31 -!- tweaks [~tweeeaks@unaffiliated/tweeeaks] has quit [Ping timeout: 240 seconds] 08:32 -!- tweaks [~tweeeaks@unaffiliated/tweeeaks] has joined #c-lightning 08:35 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Quit: %bye%] 08:36 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning 08:42 -!- fusion45 [~fusion44@128.90.20.18] has joined #c-lightning 09:04 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving] 09:20 -!- fusion45 [~fusion44@128.90.20.18] has quit [Remote host closed the connection] 09:47 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 09:48 -!- _mr_e [1872418f@gateway/web/freenode/ip.24.114.65.143] has quit [Ping timeout: 260 seconds] 09:57 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 10:11 -!- _mr_e [1872418f@gateway/web/freenode/ip.24.114.65.143] has joined #c-lightning 10:25 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 10:25 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 10:27 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Read error: Connection reset by peer] 10:27 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 10:38 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Quit: Leaving] 10:42 -!- deusexbeer [~deusexbee@095-129-175-233-dynamic-pool-adsl.wbt.ru] has quit [Quit: Konversation terminated!] 10:49 -!- grafcaps [~haroldbr@104.137.194.255] has joined #c-lightning 11:06 < grafcaps> I've got a rather old channel that is not connected and has been in "CHANNELD_SHUTTING_DOWN" for a while now. I was able to force all of the other channels to close, but this one says "bad-txns-vout-empty?" whenever I try to force-close it 12:42 -!- booyah [~bb@193.25.1.157] has quit [Ping timeout: 256 seconds] 12:46 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 12:53 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 12:53 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 12:54 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 12:56 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 12:57 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 13:01 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 13:14 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 13:35 -!- Xian001 [~xian001@47.184.129.94] has quit [] 13:44 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 248 seconds] 13:46 -!- kabaum [~kabaum@2.69.139.113.mobile.tre.se] has joined #c-lightning 13:56 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Remote host closed the connection] 13:56 -!- simlay_ [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning 14:38 -!- kabaum [~kabaum@2.69.139.113.mobile.tre.se] has quit [Ping timeout: 256 seconds] 14:39 -!- _mr_e [1872418f@gateway/web/freenode/ip.24.114.65.143] has quit [Ping timeout: 260 seconds] 14:55 < molz> grafcaps, i think it means the channel doesn't have enough to pay for the closing fee 14:55 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 15:02 < grafcaps> interesting, unfortunately I gotta run but thanks 15:09 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 240 seconds] 15:21 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 15:26 -!- grafcaps [~haroldbr@38.109.179.2] has joined #c-lightning 15:30 -!- grafcaps [~haroldbr@38.109.179.2] has quit [Ping timeout: 260 seconds] 15:33 -!- grafcaps [~haroldbr@38.109.179.2] has joined #c-lightning 15:38 -!- grafcaps [~haroldbr@38.109.179.2] has quit [Ping timeout: 240 seconds] 15:42 -!- grafcaps [~haroldbr@38.109.179.2] has joined #c-lightning 15:46 -!- grafcaps [~haroldbr@38.109.179.2] has quit [Ping timeout: 240 seconds] 15:51 -!- grafcaps [~haroldbr@38.109.179.2] has joined #c-lightning 15:55 -!- grafcaps [~haroldbr@38.109.179.2] has quit [Ping timeout: 240 seconds] 16:18 -!- grafcaps [~haroldbr@38.109.179.2] has joined #c-lightning 16:22 -!- grafcaps [~haroldbr@38.109.179.2] has quit [Ping timeout: 245 seconds] 16:27 -!- grafcaps [~haroldbr@38.109.179.2] has joined #c-lightning 16:32 -!- grafcaps [~haroldbr@38.109.179.2] has quit [Ping timeout: 256 seconds] 16:52 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 268 seconds] 16:52 < ctrlbreak> Interesting... my Eclair channel to my personal node finally appears to have blown up today: 16:52 < ctrlbreak> "status": [ 16:52 < ctrlbreak> "CHANNELD_NORMAL:HTLC 13 state SENT_REMOVE_HTLC not failed/fulfilled", 16:52 < ctrlbreak> "CHANNELD_NORMAL:Sent reestablish, waiting for theirs" 16:53 < ctrlbreak> meanwhile... Eclair says closing - uncooperative. 16:54 -!- grafcaps [~haroldbr@38.109.179.2] has joined #c-lightning 16:59 < ctrlbreak> grafcaps: you there? 16:59 -!- grafcaps [~haroldbr@38.109.179.2] has quit [Ping timeout: 260 seconds] 17:03 -!- grafcaps [~haroldbr@38.109.179.2] has joined #c-lightning 17:08 -!- grafcaps [~haroldbr@38.109.179.2] has quit [Ping timeout: 256 seconds] 17:12 -!- grafcaps [~haroldbr@38.109.179.2] has joined #c-lightning 17:17 -!- grafcaps [~haroldbr@38.109.179.2] has quit [Ping timeout: 265 seconds] 17:21 -!- grafcaps [~haroldbr@38.109.179.2] has joined #c-lightning 17:26 -!- grafcaps [~haroldbr@38.109.179.2] has quit [Ping timeout: 260 seconds] 17:30 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 17:30 -!- grafcaps [~haroldbr@38.109.179.2] has joined #c-lightning 17:34 -!- grafcaps [~haroldbr@38.109.179.2] has quit [Ping timeout: 240 seconds] 17:40 -!- grafcaps [~haroldbr@38.109.179.2] has joined #c-lightning 17:43 -!- cncr04s [~cncr04s@unaffiliated/cncr04s] has quit [Ping timeout: 255 seconds] 17:44 -!- grafcaps [~haroldbr@38.109.179.2] has quit [Ping timeout: 260 seconds] 17:46 -!- cncr04s [~cncr04s@unaffiliated/cncr04s] has joined #c-lightning 17:49 -!- grafcaps [~haroldbr@38.109.179.2] has joined #c-lightning 17:53 -!- grafcaps [~haroldbr@38.109.179.2] has quit [Ping timeout: 240 seconds] 17:58 -!- grafcaps [~haroldbr@38.109.179.2] has joined #c-lightning 18:00 < blockstream_bot> [Chang Li, Blockstream] hi team, is there a way I can monitor other people's transcations that flows through my channels ? 18:02 -!- grafcaps [~haroldbr@38.109.179.2] has quit [Ping timeout: 264 seconds] 18:07 -!- grafcaps [~haroldbr@38.109.179.2] has joined #c-lightning 18:15 * rusty wonders where blockstream_bot came from... 18:16 -!- grafcaps [~haroldbr@38.109.179.2] has quit [Ping timeout: 256 seconds] 18:16 < rusty> There's no API for that; you can see some results from listpeers, but not a complete list 18:35 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 18:39 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 240 seconds] 19:21 < windsok> does anyone know which file I need to copy to move the c-lightning on-chain wallet to another node (assuming I have no channels open) 19:22 < windsok> rusty: it seems to be a bridge the the Blockstream Slack 19:34 -!- ken2812221 [~User@133-203.dorm.ncu.edu.tw] has quit [Read error: Connection reset by peer] 19:43 -!- ken2812221 [~User@133-203.dorm.ncu.edu.tw] has joined #c-lightning 19:51 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 256 seconds] 20:23 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 20:27 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 268 seconds] 20:35 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 20:36 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 20:41 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 20:48 -!- rodarmor [sid210835@gateway/web/irccloud.com/x-srkejydsozfgaquv] has quit [Ping timeout: 256 seconds] 20:49 -!- rompert [sid13298@gateway/web/irccloud.com/x-yqwybpbfkhzvfvah] has quit [Ping timeout: 256 seconds] 20:49 -!- NicolasDorier [sid129442@gateway/web/irccloud.com/x-pptglydoyqicaryj] has quit [Ping timeout: 256 seconds] 20:50 -!- udiWertheimer [sid190185@gateway/web/irccloud.com/x-hlkjksqmxbujvran] has quit [Ping timeout: 256 seconds] 20:50 -!- takinbo [sid19838@gateway/web/irccloud.com/x-prweeqrvibnywwew] has quit [Ping timeout: 255 seconds] 20:52 -!- izgzhen [sid161198@gateway/web/irccloud.com/x-lelfaxhgfwfgcvuz] has quit [Ping timeout: 256 seconds] 21:13 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 21:16 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 21:24 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 21:48 -!- grubles [~grubles@unaffiliated/grubles] has quit [Quit: Leaving] 22:03 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 22:06 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning 22:07 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Read error: Connection reset by peer] 22:07 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 22:24 -!- rompert [sid13298@gateway/web/irccloud.com/x-zdsghatfxaodfuwc] has joined #c-lightning 22:32 -!- izgzhen [sid161198@gateway/web/irccloud.com/x-vgwqvihjllsdqxav] has joined #c-lightning 22:32 -!- udiWertheimer [sid190185@gateway/web/irccloud.com/x-fjaeobnmiefmccfj] has joined #c-lightning 22:36 -!- takinbo [sid19838@gateway/web/irccloud.com/x-phsmqbhmwhyldpth] has joined #c-lightning 22:40 -!- tiagotrs [~user@p5DDB5363.dip0.t-ipconnect.de] has joined #c-lightning 22:40 -!- tiagotrs [~user@p5DDB5363.dip0.t-ipconnect.de] has quit [Changing host] 22:40 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 22:43 < rusty> windsok: Hmm, hmm.... copy the sqlite3 file, and probably the gossip_store. The hsm_secret is the secret to the node_id, and all the channels. But if no channels are open it shouldn't matter. 22:43 < rusty> windsok: actually, the addresses are also derived from hsm_secret, so that won't work. 22:44 < rusty> windsok: on-chain xfer of funds is the easiest way to send money from one node to another, otherwise you need to do a clone (which you can't do if you want to run both!) 22:47 < sturles> Bump: https://0bin.net/paste/FXlOSzOXLUAQ-9kV#wC4T3aHSOT-fPo6WCJusX6YxlzACWVnsbwxoNr0Ei4s 22:48 < sturles> What causes this error from make check? 22:48 < sturles> Built on an oldish Debian box. 22:53 -!- rodarmor [sid210835@gateway/web/irccloud.com/x-upuudsmnongtnldq] has joined #c-lightning 22:55 -!- udiWertheimer [sid190185@gateway/web/irccloud.com/x-fjaeobnmiefmccfj] has quit [Ping timeout: 276 seconds] 22:56 -!- rompert [sid13298@gateway/web/irccloud.com/x-zdsghatfxaodfuwc] has quit [Ping timeout: 256 seconds] 22:56 < rusty> sturles: hmm, looking now... 22:56 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 22:57 -!- takinbo [sid19838@gateway/web/irccloud.com/x-phsmqbhmwhyldpth] has quit [Ping timeout: 276 seconds] 22:57 -!- izgzhen [sid161198@gateway/web/irccloud.com/x-vgwqvihjllsdqxav] has quit [Ping timeout: 276 seconds] 22:58 -!- rodarmor [sid210835@gateway/web/irccloud.com/x-upuudsmnongtnldq] has quit [Ping timeout: 255 seconds] 23:00 < rusty> sturles: hilarious, someone actually used one of the test codes to run up a machine on testnet, so the dns resolver actually returned a real address! 23:01 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 245 seconds] 23:01 < sturles> :-D 23:09 < rusty> You @sturles on GH BTW? 23:10 < sturles> Yes 23:12 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #1600: pytest: make test_connect use an unknown id. (master...make-test-connect-more-robust) https://git.io/fs3Fy 23:13 < rusty> Thanks! ^ 23:14 < sturles> Thank you too! I can upgrade my main node now. It worked on my other node for some reason. I should probably worry about that. :-) 23:15 < rusty> sturles: no, it's OK, that doesn't resolve for me now either. The node has obviously gone away... 23:17 -!- udiWertheimer [sid190185@gateway/web/irccloud.com/x-yntvrixqlhmhazfs] has joined #c-lightning 23:19 -!- rodarmor [sid210835@gateway/web/irccloud.com/x-nyevldfqfpusjuyc] has joined #c-lightning 23:20 -!- rodarmor [sid210835@gateway/web/irccloud.com/x-nyevldfqfpusjuyc] has quit [Max SendQ exceeded] 23:21 -!- rodarmor [sid210835@gateway/web/irccloud.com/x-hmxkdgcpcuxdkalo] has joined #c-lightning 23:21 -!- NicolasDorier_ [sid129442@gateway/web/irccloud.com/x-qdejdtetwaoavkex] has joined #c-lightning 23:21 -!- izgzhen [sid161198@gateway/web/irccloud.com/session] has joined #c-lightning 23:22 -!- izgzhen [sid161198@gateway/web/irccloud.com/session] has quit [Changing host] 23:22 -!- izgzhen [sid161198@gateway/web/irccloud.com/x-lenckptkjoaqxhik] has joined #c-lightning 23:22 -!- rodarmor [sid210835@gateway/web/irccloud.com/x-hmxkdgcpcuxdkalo] has quit [Max SendQ exceeded] 23:22 -!- takinbo [sid19838@gateway/web/irccloud.com/x-qfssmoijxnzmlvbo] has joined #c-lightning 23:23 -!- rodarmor [sid210835@gateway/web/irccloud.com/x-xfwebrleqflziklj] has joined #c-lightning 23:23 -!- ken2812221 [~User@133-203.dorm.ncu.edu.tw] has quit [Read error: Connection reset by peer] 23:24 -!- rompert [sid13298@gateway/web/irccloud.com/x-bxjcwzhkotculhqh] has joined #c-lightning 23:25 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 276 seconds] 23:43 -!- ken2812221 [~User@133-203.dorm.ncu.edu.tw] has joined #c-lightning 23:56 -githubby:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/fswvU 23:56 -githubby:#c-lightning- lightning/master 85e0212 arowser: align generate wire template 23:58 < sturles> rusty: it didn't fix the problem. :-( Ran make check again with the patch. Got the same error.