--- Log opened Fri Jul 09 00:00:01 2021 00:12 < cdecker[m]> Shing: all contributions are welcome, feel free to just start hacking and let us know if you need any help. 00:14 < Shing> thanks, cdecker[m]! 00:15 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has joined #c-lightning 00:32 -!- kon__ [~kon@p200300d4a723ba00f8452ece978b29be.dip0.t-ipconnect.de] has joined #c-lightning 00:32 -!- Shing [~Shing@c-71-197-149-235.hsd1.wa.comcast.net] has quit [Quit: Client closed] 00:54 -!- kon__ [~kon@p200300d4a723ba00f8452ece978b29be.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds] 00:55 -!- k3tan [~pi@user/k3tan] has quit [Ping timeout: 272 seconds] 00:57 -!- k3tan [~pi@user/k3tan] has joined #c-lightning 01:10 -!- kon__ [~kon@p200300d4a723ba00f8452ece978b29be.dip0.t-ipconnect.de] has joined #c-lightning 01:30 -!- kon__ [~kon@p200300d4a723ba00f8452ece978b29be.dip0.t-ipconnect.de] has quit [Read error: Connection reset by peer] 01:31 -!- kon__ [~kon@p50882086.dip0.t-ipconnect.de] has joined #c-lightning 01:44 -!- kon[m]1 [~konnixbit@2001:470:69fc:105::b9af] has joined #c-lightning 01:44 -!- kon__ [~kon@p50882086.dip0.t-ipconnect.de] has quit [Quit: Leaving] 02:51 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 02:57 -!- jarthur [~jarthur@2603-8080-1540-002d-51f6-604d-705f-f753.res6.spectrum.com] has quit [Ping timeout: 252 seconds] 03:05 -!- jarthur [~jarthur@2603-8080-1540-002d-d976-268d-ebd6-fd0d.res6.spectrum.com] has joined #c-lightning 04:57 < nathanael> the feerate from fundchannel is in msats right? i don't think this is clear from reading lightning-fundchannel(7) 05:02 < nathanael> what i mean is feerate=1000 1 sat-per-kilobyte or 1000 sat-per-kilobytte? 05:03 < nathanael> from the docs: 05:03 < nathanael> and perkb means it is interpreted bitcoind-style as satoshi-per-kilobyte. Omitting the suffix is equivalent to perkb. 05:07 < nathanael> found the answer i guess: https://bitcoin.stackexchange.com/questions/106333/different-fee-rate-units-sat-vb-sat-perkw-sat-perkb 06:28 -!- fiatjaf [~fiatjaf@2804:7f2:2a8b:8bee:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 252 seconds] 06:29 -!- fiatjaf [~fiatjaf@2804:7f2:2a8b:8bee:ea40:f2ff:fe85:d2dc] has joined #c-lightning 06:36 -!- fiatjaf [~fiatjaf@2804:7f2:2a8b:8bee:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 252 seconds] 06:37 -!- fiatjaf [~fiatjaf@2804:7f2:2a8b:8bee:ea40:f2ff:fe85:d2dc] has joined #c-lightning 07:38 < nathanael> cdecker[m]: is this once more the situation where the log makes me feel there is something wrong but it isn't: 07:38 < nathanael> https://tmp.dalliard.ch/60e85f3c583929b6.txt 08:02 < nathanael> and this means i have to wait: CHANNELD_AWAITING_LOCKIN:Sent reestablish, waiting for theirs 08:05 < cdecker[m]> Yeah, they should send a re-establish message whenever we reconnect with a channel (confirmed or not), seems they aren't sending that, which I've seen a couple of times when the channel wasn't confirmed yet (no idea which impl and which version). Hopefully they will once the channel is confirmed and locked in (at most 6 confirmations). 08:05 < cdecker[m]> The logs look alright, they just keep disconnecting (again with the alarming log messages xD) 08:12 < nathanael> thanks cdecker[m] - i have to get used to the messages 08:12 < nathanael> the peer runs lnd 08:12 < nathanael> and yes the tx is not yet confirmed 08:41 < nathanael> is this a bug? i can't ping the peer i am in the process of opening a channel 08:41 < nathanael> i also can't disconnect because i am in the state of channeld_awaiting_lockin 08:42 < nathanael> that maybe explains why the other node can't "accept" 10:55 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 244 seconds] 10:55 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning 11:52 -!- valwal [~valwal@96.224.58.144] has joined #c-lightning 12:20 -!- Guest67 [~Guest67@142.68.207.230] has joined #c-lightning 12:47 -!- Guest67 [~Guest67@142.68.207.230] has quit [Quit: Ping timeout (120 seconds)] 13:42 -!- Guest11 [~Guest11@142.68.207.230] has joined #c-lightning 13:46 < Guest11> I have a quick question about python plugins in c-lightning. When I launch lightningd with plugins, it seems to be reading in an older version of the pyln-client module (from the folder I built c-lightning in), rather than wherever pip installed the newer version to. 13:46 < Guest11> PYTHONPATH is empty, and I removed the path for the old one from sys.path in python. 13:50 < Guest11> When c-lightning launches a python plugin, does it do anything underneath the hood to add a path to sys.path? I can't figure out why it is still loading it from my build directory even after removing that path from sys.path 13:52 -!- aechu [~major@gateway/tor-sasl/major] has joined #c-lightning 13:53 < darosior> No, it will `exec` the plugin so it depends on it. Usually Python plugins have a schebang like `#!/usr/bin/en python`. What plugin are you trying to start? It's weird to me that it would use the source repo as first path.. 13:54 < Guest11> It is the rebalance plugin 13:55 < Guest11> https://github.com/lightningd/plugins/tree/master/rebalance 13:55 < Guest11> #!/usr/bin/env python3 14:03 < darosior> What error do you have? 14:03 < darosior> Try simply running `#!/usr/bin/env python3 rebalance.py` to debug 14:03 < Guest11> Thanks for your help darosior, it helped me solve the issue. 14:04 < darosior> Oh, cool. yw 14:04 < Guest11> The issue was when I would restart lightningd to test it out, that terminal window that lightningd was in still had PYTHONPATH set to include the old module path 14:04 < Guest11> (since i *just* removed it from my .bashrc) 14:04 < Guest11> So I manually changed PYTHONPATH in the lightningd terminal window and it took care of the problem 14:05 < Guest11> I know just enough to be dangerous haha 14:05 < darosior> :) 14:10 -!- Guest11 [~Guest11@142.68.207.230] has quit [Quit: Client closed] 15:03 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 244 seconds] 15:05 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning 16:32 -!- jasan [~j@adsl-dyn213.78-98-68.t-com.sk] has quit [Ping timeout: 240 seconds] 17:14 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has quit [Ping timeout: 272 seconds] 17:22 -!- belcher_ [~belcher@user/belcher] has joined #c-lightning 17:26 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 272 seconds] 18:37 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning 20:08 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 255 seconds] 21:07 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 23:17 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning 23:24 -!- Netsplit *.net <-> *.split quits: sword_smith, michaelfolkson, ufotofu, niftynei, _aj_, gijswijs 23:25 -!- Netsplit over, joins: _aj_, michaelfolkson, ufotofu, niftynei, sword_smith, gijswijs 23:52 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 252 seconds] 23:56 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 244 seconds] --- Log closed Sat Jul 10 00:00:02 2021