--- Log opened Wed Aug 14 00:00:40 2019
00:42 -!- RonNa [~quassel@60-251-129-61.HINET-IP.hinet.net] has quit [Ping timeout: 245 seconds]
00:43 -!- RonNa [~quassel@60-251-129-61.HINET-IP.hinet.net] has joined #c-lightning
01:06 < t0mix> meeDamian: "lightning-cli getinfo|grep height; bitcoin-cli -getinfo|grep blocks" should return same numbers
01:08 < t0mix> it happened to me, I started cln before the bitcoind. I ended up waiting long hours syncing.
01:39 -!- meeDamian [52661934@82.102.25.52] has joined #c-lightning
01:40 -!- meeDamian [52661934@82.102.25.52] has quit [Remote host closed the connection]
02:47 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
03:56 < rusty> cdecker: if you could ack https://github.com/ElementsProject/lightning/pull/2953 I'll merge it once it passes (assuming it doesn't time out!) then can rebase on top.
04:32 -!- queip [~queip@unaffiliated/rezurus] has quit [Quit: bye, freenode]
04:47 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
05:00 -!- meeDamian [7a9bae40@122.155.174.64] has joined #c-lightning
05:13 -!- meeDamian [7a9bae40@122.155.174.64] has quit [Ping timeout: 260 seconds]
05:18 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
05:26 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has left #c-lightning []
05:26 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has joined #c-lightning
05:30 -!- designwish [~designwis@51.ip-51-68-136.eu] has quit [Quit: ZNC - http://znc.in]
05:39 -!- designwish [~designwis@51.ip-51-68-136.eu] has joined #c-lightning
05:45 -!- backpacker69 [~backpacke@mx-spb.adriver.ru] has joined #c-lightning
05:47 < backpacker69> greetings everyone, i’m playing with latest c-lightning and keep getting  Bad commit_sig signature 3 errors on the channel at random intervals
05:47 < backpacker69> sometimes i can get 10 payments go through, sometimes only 1, but eventually it will always end with bad commit_signature on the payer side
06:26 -!- Amperture [~amp@24.136.5.183] has quit [Read error: Connection reset by peer]
06:57 -!- justanotheruser [justanothe@gateway/vpn/nordvpn/justanotheruser] has quit [Ping timeout: 268 seconds]
07:02 < backpacker69> most of the errors happen on SENT_REMOVE_REVOCATION->SENT_REMOVE_ACK_COMMIT change
07:06 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection]
07:07 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
07:18 -!- justanotheruser [justanothe@gateway/vpn/nordvpn/justanotheruser] has joined #c-lightning
07:22 -!- justanotheruser [justanothe@gateway/vpn/nordvpn/justanotheruser] has quit [Quit: WeeChat 2.4]
07:26 -!- justanotheruser [justanothe@gateway/vpn/nordvpn/justanotheruser] has joined #c-lightning
07:49 <@cdecker> backpacker69: Any idea what the implementation the other end is running? lnd had a timing issue a while ago that could result in a signature for an empty update if you performed a number of payments too quickly
12:20 -!- reallll [~belcher@unaffiliated/belcher] has joined #c-lightning
12:22 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
12:22 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Write error: Connection reset by peer]
12:22 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Write error: Connection reset by peer]
12:23 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 248 seconds]
12:24 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
12:24 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
12:25 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
12:54 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
12:54 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
13:34 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has left #c-lightning []
13:35 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has joined #c-lightning
14:07 -!- btcbrother [25d1127e@37.209.18.126] has joined #c-lightning
14:08 -!- btcbrother [25d1127e@37.209.18.126] has left #c-lightning []
14:11 -!- btcbrother [~simon@ip-109-42-3-85.web.vodafone.de] has joined #c-lightning
16:09 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
16:27 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
16:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
17:07 < rusty> niftynei: https://github.com/ElementsProject/lightning/pull/2954 so you have an old payment in your db?
17:07 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
17:09 <@niftynei> i think so
17:10 <@niftynei> i queried the db and the payment_hash field is empty
17:11 <@niftynei> for one of the payments
17:11 < rusty> Yeah, 6d333f16cc0f3aac7097269bf0985b5fa06d59b4
17:11 < rusty> But the correct fix is to omit the field in the JSON, IMHO.
17:12 < rusty> Want me to respin, since you're chasing a different ghost?
17:12 < rusty> niftynei: ^
17:12 <@niftynei> sure! 
17:12 <@niftynei> sgtm re: removing the field
17:13 <@niftynei> that's definitely better for consumers than putting in 'garbage' data strings like 'unknown'
17:18 < rusty> Hmm, similar issues with scid fields, BTW.  They'll be zero, so we won't crash, but we should omit them.  Testing here...
17:19 < rusty> Heh, yes, liftforwards is crashing my node right now...
17:42 < rusty> Yuck, fixed the other fields, but it makes listforwards less useful.  I wonder if cdecker wants to delete less from the db in future here?
17:44 < rusty> niftynei: OK, #2954 ready for re-review....
17:54 < rusty> Travis still too slow... considering adding -Og to dev tests.  That generally makes life easier for valgrind, but am measuring performance difference now.
18:10 <@niftynei> just saw this, looking now
18:17 <@niftynei> i'm starting to wonder if exposing the failcode to plugins is a good idea. c-lightning is really good about replying with the correct failcode for any given situation; exposing every possible reason to the discretion of an external dev seems like a lot of potential for confusion 
18:19 <@niftynei> defaulting to a node error code or limiting them to a subset might be more reasonable
18:45 < rusty> Yeah, I got confused over what fields are present, too.  Force pushed the fix.
18:46 < rusty> Only the payment_hash may be missing due to deletion later.  The output fields can be missing because we local_failed before we determined where HTLC was going.
19:08 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection]
19:09 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
19:12 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning
19:20 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning
19:47 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Read error: Connection reset by peer]
19:47 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
19:47 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
19:57 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has left #c-lightning []
19:57 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has joined #c-lightning
20:21 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has quit [Ping timeout: 244 seconds]
20:23 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has joined #c-lightning
21:03 < rusty2> mail.r
21:03 -!- rusty2 is now known as rusty
21:27 -!- mode/#c-lightning [+o rusty] by ChanServ
21:27 -!- rusty changed the topic of #c-lightning to: Chat about the C-lightning implementation: https://github.com/ElementsProject/lightning https://lists.ozlabs.org/listinfo/c-lightning  Current Version: https://github.com/ElementsProject/lightning/releases/tag/v0.7.2rc2 (please test!) Logs at http://gnusha.org/c-lightning/
21:27 -!- mode/#c-lightning [-o rusty] by rusty
22:28 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
22:45 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
--- Log closed Thu Aug 15 00:00:40 2019