--- Log opened Tue Sep 08 00:00:13 2020 00:05 -!- vadorovsky__ [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection] 00:06 -!- vadorovsky__ [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 00:15 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection] 00:28 -!- reallll [~belcher@unaffiliated/belcher] has joined #c-lightning 00:30 < m-schmoock> rusty: regarding https://github.com/ElementsProject/lightning/wiki Do you mean release 0.9.1 in this list? 00:30 < m-schmoock> or 0.9.2 for upcoming stuff? 00:31 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 265 seconds] 00:38 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 01:01 -!- k3tan172 [~pi@gateway/tor-sasl/k3tan] has quit [Ping timeout: 240 seconds] 01:03 -!- MasterdonX [~masterdon@37.120.212.76] has quit [Ping timeout: 256 seconds] 01:04 -!- k3tan172 [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning 01:05 -!- MasterdonX [~masterdon@37.120.212.76] has joined #c-lightning 01:21 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 01:22 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 01:28 -!- vadorovsky__ [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection] 01:29 -!- vadorovsky__ [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 01:44 < m-schmoock> i fixed my audio issues :D at least I know what caused it 01:44 < m-schmoock> audio jack switch in my new laptop triggers an invalid state switch in pulseaudio 01:44 < zmnscpxj_> C-Lightning caused audio issues? 01:44 < m-schmoock> ^^ 01:44 < m-schmoock> zmnscpxj_: my audio was broken yesterday in the jitsy meeting 01:44 < m-schmoock> (unrelated) 01:45 < zmnscpxj_> ah 01:52 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 01:53 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 01:55 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 01:56 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 01:59 -!- jonatack [~jon@192.113.14.109.rev.sfr.net] has joined #c-lightning 02:05 -!- jonatack [~jon@192.113.14.109.rev.sfr.net] has quit [Ping timeout: 246 seconds] 02:06 -!- jonatack [~jon@37.172.68.103] has joined #c-lightning 02:22 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 02:41 < m-schmoock> @all: do we want to have a 'channelstate_hook' on which plugins are notified i.e. to 'state' changes (old state, new state) for a channel? 02:42 < zmnscpxj_> why hook? what can a plugin do to change that? 02:42 < m-schmoock> nothing, but it gets notified without polling if a channel closes i.e. 02:42 < zmnscpxj_> why not a notification instead of a hook? 02:42 < zmnscpxj_> I mean 02:42 < m-schmoock> lets say notification instead of hook 02:42 < m-schmoock> yes 02:42 < m-schmoock> maybe i meant that 02:43 < zmnscpxj_> ok 02:43 < m-schmoock> lets call it channelstate_notification 02:45 < zmnscpxj_> since it is about a change in channel state, why not `channel_state_changed`? 02:45 -!- skme9 [~skme9@2402:3a80:6bd:e69f:e823:50f0:93d0:63df] has joined #c-lightning 02:45 < m-schmoock> yes something like this. fiatjaf asked something like that yesterday on twitter 02:46 < zmnscpxj_> okay 02:46 < m-schmoock> I can imagine that might be helpful for monitoring plugins and such 02:46 < zmnscpxj_> yes 02:46 < m-schmoock> ill open an issue 02:48 < zmnscpxj_> does anyone know of a nice way to get around ISP for DNS SRV queries? `dig r0.lseed.bitcoinstats.com SRV` from my direct connection returns "no servers can be reached", but using remote tools suggests it is only my ISP 02:52 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 02:53 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 02:55 < m-schmoock> zmnscpxj_: nope sry. Regarding channel_state_changed I added feature request https://github.com/ElementsProject/lightning/issues/4018 02:59 < az0re> zmnscpxj_: Maybe a stupid question but did you try another DNS server? `dig @1.1.1.1 r0.lseed.bitcoinstats.com SRV` 03:00 < zmnscpxj_> that works, thanks 03:00 < az0re> np 03:01 -!- sr_gi [~sr_gi@static-240-45-224-77.ipcom.comunitel.net] has joined #c-lightning 03:13 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 03:14 < rusty> m-schmoock: clarified :) 03:14 < m-schmoock> thx 03:16 < m-schmoock> Then I might add 4005 and 4018 to the list. Not sure If I can make 3550. I simply add them and I see how far I get with them 03:19 < m-schmoock> rusty: added some items i will be working on 03:20 < m-schmoock> what date is planned for the 0.9.2 release? 03:21 -!- rotarydialer [~rotarydia@unaffiliated/rotarydialer] has quit [Ping timeout: 256 seconds] 03:23 < darosior> Argh Travis can't handle ASAN.. 03:28 < darosior> And i need to force push to play with it.. :/ 03:29 -!- rotarydialer [~rotarydia@unaffiliated/rotarydialer] has joined #c-lightning 03:36 < rusty> m-schmoock: we aim for -rc1 on the 10th of every second month. So 0.9.1-rc1 September 10 2020. Hence 0.9.2 freezes about November 10? 03:37 < m-schmoock> thx. thats great as I will start to have a lot more time as of early October 03:45 -!- rotarydialer [~rotarydia@unaffiliated/rotarydialer] has quit [Ping timeout: 258 seconds] 03:47 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 03:52 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 264 seconds] 03:53 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 03:56 -!- jonatack [~jon@37.172.68.103] has quit [Ping timeout: 264 seconds] 03:57 -!- jonatack [~jon@213.152.161.211] has joined #c-lightning 03:59 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 03:59 -!- rotarydialer [~rotarydia@unaffiliated/rotarydialer] has joined #c-lightning 04:01 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 04:12 -!- jonatack [~jon@213.152.161.211] has quit [Ping timeout: 240 seconds] 04:38 -!- vadorovsky__ [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds] 04:40 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 05:31 -!- reallll is now known as belcher 05:55 -!- vincenzopalazzo [~vincent@host-79-35-119-77.retail.telecomitalia.it] has quit [Ping timeout: 240 seconds] 06:02 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 240 seconds] 06:10 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning 06:16 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning 06:27 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 260 seconds] 06:36 -!- k3tan172 is now known as k3tan 06:45 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 06:54 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 07:12 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection] 07:12 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection] 07:13 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 07:15 -!- sr_gi [~sr_gi@static-240-45-224-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer] 07:15 -!- sr_gi [~sr_gi@static-240-45-224-77.ipcom.comunitel.net] has joined #c-lightning 07:34 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Read error: Connection reset by peer] 07:34 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning 07:44 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 07:45 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 08:01 -!- queip [~queip@unaffiliated/rezurus] has quit [Quit: bye, freenode] 08:04 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 09:11 -!- alko89 [~alko89@unaffiliated/alko89] has quit [Quit: ZNC 1.7.5 - https://znc.in] 09:11 -!- alko89 [~alko89@unaffiliated/alko89] has joined #c-lightning 09:21 < m-schmoock> cdecker: do we want the channel_state_changed notification also for 0.9.1 release ? https://github.com/ElementsProject/lightning/pull/4020 09:22 <@cdecker> Hm, rusty is in charge for the release, so he'll make the final call on that one, I'll ping him to see what he thinks 09:22 < m-schmoock> sure 09:30 < m-schmoock> meanwhile ill add another that checks this message for unilateral close 09:31 < m-schmoock> *test 09:43 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds] 09:51 -!- skme9 [~skme9@2402:3a80:6bd:e69f:e823:50f0:93d0:63df] has quit [Ping timeout: 244 seconds] 10:03 < m-schmoock> done. travis should be happy now 10:10 < az0re> What is the `AVAIL` column in the `summary` output? My `avail_out` hasn't changed but my channel peers' `AVAIL` column has 10:22 < m-schmoock> this is availability 10:22 < m-schmoock> meaning the % percentage the peer has been online the last 72hrs (iirc) 10:38 -!- skme9 [~skme9@2402:3a80:6bd:e69f:e823:50f0:93d0:63df] has joined #c-lightning 10:41 < az0re> Aha, *that* kind of availability. Thanks. 10:47 -!- skme9 [~skme9@2402:3a80:6bd:e69f:e823:50f0:93d0:63df] has quit [Ping timeout: 260 seconds] 11:18 < jasan> zmnscpxj_ regarding that ISP DNS SRV filtering, did you try something like `dig r0.lseed.bitcoinstats.com SRV @1.1.1.1` ? 11:25 -!- skme9 [~skme9@2402:3a80:6bd:e69f:e823:50f0:93d0:63df] has joined #c-lightning 11:25 -!- sr_gi [~sr_gi@static-240-45-224-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer] 11:26 -!- sr_gi [~sr_gi@static-240-45-224-77.ipcom.comunitel.net] has joined #c-lightning 11:31 -!- skme9 [~skme9@2402:3a80:6bd:e69f:e823:50f0:93d0:63df] has quit [Ping timeout: 260 seconds] 12:00 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 258 seconds] 12:42 < m-schmoock> fiatjaf: hm, let me check 12:44 < m-schmoock> I think it would not be nice code-wise. maybe this can be added after the basic functionality is done 12:48 < m-schmoock> cdecker: I discovered that currently channel_set_state will be called two times with the same new_state AWAITING_UNILATERAL 12:49 < m-schmoock> (at least if channel is forced closed) 12:49 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 13:01 < m-schmoock> fiatjaf: regarding state change 'reason' maybe you want to know if the user closed the channel on demand or if its a remote cause. I will think about this. 13:01 < m-schmoock> not sure yet 13:10 < az0re> Whenever I try to send a greater-than-trivial amount, I get a whole host of failures, mostly {"status": "pending", "failreason": "Error computing a route to ...: \"Could not find a route\" (205)" ... } 13:11 < az0re> What's going wrong here? 13:13 -!- rotarydialer [~rotarydia@unaffiliated/rotarydialer] has quit [Ping timeout: 240 seconds] 13:20 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Ping timeout: 265 seconds] 13:24 < m-schmoock> az0re: likely your node is not well connected. if it runs out of options to find routes for this amount it eventually raises this error 13:25 < m-schmoock> how many channels does it have? If its just one or two, how many channels do these peer have? 13:29 < az0re> I have four open channels 13:29 -!- rotarydialer [~rotarydia@unaffiliated/rotarydialer] has joined #c-lightning 13:29 < fiatjaf> az0re, m-schmoock: I think that may be caused by the way c-lightning splits payments. too many shards are likely to cause too much base_fee paid. I've recompiled my node setting the minimum shard size to 100000sat and am not getting these weird errors anymore. 13:29 < fiatjaf> m-schmoock: thank you for looking at it! 13:29 < az0re> One of which is with lnbig.com, although slightly less (spendable) than the amount I want to send 13:30 < m-schmoock> fiatjaf: whats the default setting for minimum shard size ? 13:30 < fiatjaf> lnbig.com is known for charging very high fees -- I think in the past he charged less but now... 13:30 < az0re> fiatjaf: I see. I also noticed an extreme number of shards 13:30 < fiatjaf> m-schmoock: 10000sat 13:31 < fiatjaf> and payments are pre-split into shards of that size before any attempt if i understood well 13:31 < az0re> m-schmoock: Thanks. And WIRE_MPP_TIMEOUT ? 13:31 < fiatjaf> m-schmoock: my reason is to know which peers are closing channels for no reason so I can block them 13:32 < fiatjaf> ideally would share information with other nodes and build a database of node reputation regarding channel closure behavior 13:32 < fiatjaf> but I'm not sure when I'll have time to work on these things, so please don't hurry because of me 13:32 < m-schmoock> fiatjaf: i see (@close reason). is someone addressing this split payment minimal sizeissue? 13:34 < m-schmoock> az0re: WIRE_MPP_TIMEOUT indicates that the payment was split an one part timed out 13:36 < az0re> And so that other part failed? 13:36 < az0re> Or it sits pending? 13:37 < m-schmoock> sorry, im not deep in that multipart payment stuff yet 13:37 < az0re> OK no problem 13:41 < m-schmoock> maybe try fiatjaf approach 13:43 < m-schmoock> fiatjaf: we dont get a reason on channel close from the remote. all we see is that the remote bilaterally closes (without further reason). However we can (by code) distinguish these closes from local RPC closes of the user itself for example. there are also some other local reasons why a channel will close 13:43 < m-schmoock> i'll sleep over it :D 13:43 < m-schmoock> just got the PR ready as is. Travis should no longer complain. 13:51 < az0re> "Peer permanent failure in CHANNELD_NORMAL: Funding transaction spent" just means my peer closed the channel, right? 14:11 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 264 seconds] 14:27 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 14:34 < m-schmoock> whohoo what happend, I can restart travis jobs \o/ 15:38 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 15:38 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Read error: Connection reset by peer] 15:59 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 15:59 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Quit: Leaving] 16:00 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 16:00 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 16:01 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 16:12 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 16:48 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 17:03 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 17:05 < rusty> zmnscpxj_: if you're happy with the various fixups! in https://github.com/ElementsProject/lightning/pull/3763 I'm looking forward to merging it! 17:06 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection] 17:09 < zmnscpxj_> looks ok 17:11 < rusty> zmnscpxj_: great, I'll squash and commit. 17:15 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection] 17:15 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 17:35 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection] 17:40 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 17:45 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 265 seconds] 17:45 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Read error: Connection reset by peer] 17:51 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 17:53 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Read error: Connection reset by peer] 18:13 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 18:15 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Remote host closed the connection] 18:16 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning 18:18 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 18:23 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 265 seconds] 18:34 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 18:35 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 18:42 -!- skme9 [~skme9@2402:3a80:6bd:e69f:f4a7:ee6:b81c:9e97] has joined #c-lightning 18:46 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 18:46 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 19:14 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has left #c-lightning [] 20:00 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Remote host closed the connection] 20:01 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning 20:19 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 20:23 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 258 seconds] 20:30 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 20:30 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 20:46 -!- jasan [~jasan@tunnel509499-pt.tunnel.tserv27.prg1.ipv6.he.net] has quit [Ping timeout: 246 seconds] 20:52 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning 20:57 -!- sr_gi [~sr_gi@static-240-45-224-77.ipcom.comunitel.net] has quit [Write error: Connection reset by peer] 20:58 -!- sr_gi6 [~sr_gi@static-240-45-224-77.ipcom.comunitel.net] has joined #c-lightning 21:03 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Quit: k3tan] 21:04 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection] 21:04 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning 21:10 -!- jasan [~jasan@dynamic-bband-83.194-212-253.telekom.sk] has joined #c-lightning 22:20 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 22:25 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 260 seconds] 22:44 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning 22:44 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 22:45 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 23:01 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 23:02 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 23:41 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 244 seconds] 23:49 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning 23:56 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Read error: Connection reset by peer] 23:56 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning --- Log closed Wed Sep 09 00:00:13 2020