--- Log opened Tue May 19 00:00:25 2020
00:38 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection]
00:39 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
01:54 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
01:55 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
02:05 -!- lxer [~lx@ip5f5bf4a3.dynamic.kabel-deutschland.de] has joined #c-lightning
02:06 < lxer> After restarting c-lightning I get this message, and it fails to start again: lightning_connectd: Connecting stream socket to Tor service: Connection refused
02:07 < lxer> lightningd: connectd failed (exit status 1), exiting.
02:07 < zmnscpxj> Is your Tor running correctly? check if there are errors in: journalctl -u tor
02:08 < zmnscpxj> hmmm I guess depends on your system haha
02:08 < zmnscpxj> but most linuxen use systemd nowadays so journalctl -u tor should work
02:09 < lxer> ok, let me check
02:29 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]
02:31 < lxer> found it. Tor was looking in the wrong folder for the config. 'Configuration file "/usr/local/etc/tor/torrc" not present, using reasonable defaults.'
02:31 < zmnscpxj> ^^
02:32 < darosior> zmnscpxj: are you still working on multifundchannel ?
02:32 < zmnscpxj> supposedly but the homegrown parallel-connect thing is not working yet, sigh....
02:33 < zmnscpxj> thinking of scrapping the code and redoing from a fresh start haha
02:33 < darosior> :/
02:33 < zmnscpxj> because if you're funding in parallel it would make more sense to do the connect handshaking in parallel as well
02:34 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
02:39 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
02:54 < darosior> Yeah, though a first version doing sequential connection is *largely* cceptable don't you think ?
02:54 < darosior> We need batching more and more every day :)
02:54 < zmnscpxj> it's supposed to serve as a test of the parallel execution framework, and we need to actually execute the fundchannel_* in parallele
02:54 < zmnscpxj> so I'm having problems with the parallel execution framework
02:55 < darosior> Wrt libplugin or the actual RPC interface ?
02:55 < zmnscpxj> fundchannel_start waits for the remote to respond
02:56 < zmnscpxj> libplugin
02:56 < darosior> Aaah
02:56 < zmnscpxj> :/
02:57 < zmnscpxj> ooooor we could do it python i mean it's not as if "C" is part of the name of the thing....
02:57 < darosior> I have a Python script to do so atm ^^
02:58 < zmnscpxj> ye but python2->3 was not nice to LTS operating systems so I really want to avoid python for a while...
02:59 < darosior> But why can't you use the same logic as we use in lightningd/plugin to start plugins ? This is kind of the same problem
02:59 < darosior> Each getmanifest waits for the plugin response
02:59 < darosior> but we send them in parallel
02:59 < zmnscpxj> it's supposed to do so, but somehow signals get crossed somewhere, sigh.
03:00 < darosior> Did you try since io_plan s in libplugin ?
03:00 < zmnscpxj> not yet
03:03 < darosior> I think there is decent probability it fixes the issue as it's the exact same logic we have in lightningd/plugin for parallel calls :)
03:21 -!- fibericon [6ffa7e26@111-250-126-38.dynamic-ip.hinet.net] has joined #c-lightning
03:29 < fibericon> Hi all. I had a question about funding channels. Once I've funded a channel, does the satoshi return to the wallet once it's closed, or do I need to do something before closing it?
03:30 < zmnscpxj> it should eventually return to the wallet some time after closing if you close it unilaterally, if it was a mutual close it should appear immediately
03:30 < zmnscpxj> no special command needed
03:30 < zmnscpxj> though it could take a day or so
03:31 < fibericon> Thanks!
03:34 < fibericon> Hmm, using lightning-cli close id seems to hang my console.
03:34 < zmnscpxj> if the counterparty is offline, it will try to wait some time before force-closing
03:35 < zmnscpxj> is the counterparty connected?
03:35 < fibericon> They are not. That would explain it.
03:36 < zmnscpxj> the default is waiting 2 days though
03:36 < zmnscpxj> hmmm
03:36 < zmnscpxj> https://lightning.readthedocs.io/lightning-close.7.html
03:36 < zmnscpxj> If unilateraltimeout is not zero, the close command will unilaterally close the channel when that number of seconds is reached. If unilateraltimeout is zero, then the close command will wait indefinitely until the peer is online and can negotiate a mutual close. The default is 2 days (172800 seconds).
03:37 < zmnscpxj> cancelling a lightning-cli command with ^C does not consistently cancel commands, I think ---- some builtin commands will get cancelled, but all(?) plugin commands definitely keep running
04:08 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]
04:12 -!- m-schmoock [~will@schmoock.net] has quit [Remote host closed the connection]
04:12 -!- m-schmoock [~will@schmoock.net] has joined #c-lightning
04:25 -!- lxer [~lx@ip5f5bf4a3.dynamic.kabel-deutschland.de] has quit [Quit: Lost terminal]
04:38 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
05:13 < darosior> zmnscpxj: which ones would be cancelled for example ?
05:15 < zmnscpxj> the ones which tal off the `cmd`, which is itself `tal`ed off the connection, which is freed automatically when SIGINT closes lightning-cli
05:15 < zmnscpxj> we'd have to audit the code actually
05:15 < zmnscpxj> I remember being careful of keeping stuff alive back when `pay` was builtin
05:16 < zmnscpxj> I
05:16 < zmnscpxj> I am not actually 100% sure what is best behavior here --- I think cancelling the command would be better since that is what people using lightning-cli would expect (maybe?)
06:05 < darosior> Yeah that's what I would expect
06:06 < zmnscpxj> plugins don't learn about the client-side command connection being killed
06:06 < zmnscpxj> so plugins cannot cancel commands
06:08 < zmnscpxj> but in terms of RPC.... if we received the command, and the client disconnects before we respond, should we cancel the command?
06:08 < darosior> Hmm I think so, why not?
06:09 < zmnscpxj> if the client was killed due to its own exception?
06:09 < zmnscpxj> should that affect lightningd?
06:12 -!- nothingmuch [~nothingmu@unaffiliated/nothingmuch] has quit [Quit: ZNC - http://znc.in]
06:15 -!- nothingmuch [~nothingmu@unaffiliated/nothingmuch] has joined #c-lightning
06:49 -!- sr_gi [~sr_gi@183.red-83-34-186.dynamicip.rima-tde.net] has quit [Ping timeout: 264 seconds]
06:58 -!- sr_gi [~sr_gi@183.red-83-34-186.dynamicip.rima-tde.net] has joined #c-lightning
07:04 -!- fibericon [6ffa7e26@111-250-126-38.dynamic-ip.hinet.net] has quit [Remote host closed the connection]
07:17 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
07:20 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
07:44 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
07:48 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
07:50 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection]
08:32 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection]
08:45 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 252 seconds]
09:01 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
09:10 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 256 seconds]
09:20 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
09:23 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
09:23 -!- vasild_ is now known as vasild
09:25 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has quit [Remote host closed the connection]
09:25 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has joined #c-lightning
09:30 -!- Educob2 [5a4ae098@90.74.224.152] has quit [Remote host closed the connection]
09:51 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
10:21 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
10:21 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
11:21 -!- afk11` [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection]
11:22 -!- afk11` [~afk11@gateway/tor-sasl/afk11] has joined #c-lightning
12:03 -!- Amperture [~amp@65.79.129.113] has joined #c-lightning
12:17 -!- Amperture [~amp@65.79.129.113] has quit [Quit: Leaving]
13:28 -!- shupfel [~Bohphah3@92.117.143.169] has joined #c-lightning
13:29 -!- shupfel [~Bohphah3@92.117.143.169] has quit [Client Quit]
13:49 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
15:13 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds]
15:32 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
15:39 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
16:03 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has quit [Remote host closed the connection]
16:04 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has joined #c-lightning
17:21 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
18:28 < fiatjaf> a pending payment doesn't show on listsendpays
18:28 < fiatjaf> so how can it show on listpays
18:29 < fiatjaf> if all listpays do is go through the list of listsendpays and modify it slightly?
18:29 < fiatjaf> what am I missing?
18:29 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
18:29 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
18:42 < fiatjaf> same for payments that are in the middle of a retry attempt by `pay`
18:43 < fiatjaf> my concrete issue is: sometimes when an outgoing payment is happening and takes too long or the node is restarted in the middle of it, the program must check if it's still pending and then delete it from the system if it's failed.
18:44 < fiatjaf> I only have the payment_hash, so I do `listsendpays -k payment_hash=<...>` and get the bolt11 there so then I can call `listpays <...>`
18:47 < fiatjaf> but sometimes the response from `listsendpays` comes empty, so I figured out that happens when the payment is not even tried, like when there are no routes
18:48 < fiatjaf> but apparently this is wrong because I've found 2 occasions now in which a payment returned an empty list on `listsendpays` but then was completed afterwards.
18:48 < fiatjaf> what am I missing?
18:49 < fiatjaf> (there should be a book on how to properly use `pay`, I've done wrong things with it infinite times at this point)
19:21 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
20:00 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has quit [Read error: Connection reset by peer]
20:01 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has joined #c-lightning
20:31 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
20:46 -!- afk11` [~afk11@gateway/tor-sasl/afk11] has quit [Ping timeout: 240 seconds]
20:49 -!- afk11` [~afk11@gateway/tor-sasl/afk11] has joined #c-lightning
21:20 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
21:23 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
21:23 -!- vasild_ is now known as vasild
22:40 -!- berndj [~berndj@azna.co.za] has quit [Ping timeout: 260 seconds]
22:51 -!- berndj [~berndj@azna.co.za] has joined #c-lightning
22:53 -!- berndj [~berndj@azna.co.za] has quit [Excess Flood]
22:53 -!- berndj [~berndj@azna.co.za] has joined #c-lightning
23:37 -!- Educob2 [5a4ae098@90.74.224.152] has joined #c-lightning
23:53 < Educob2> Hi. I have two regtest nodes. I can pay invoices created by node 2 (payment node 1 -> node 2) .But when I try to pay an invoice created by node 1 (node 2 -> node 1) I get error: 205 "Could not find a route"
23:54 -!- sr_gi [~sr_gi@183.red-83-34-186.dynamicip.rima-tde.net] has quit [Ping timeout: 246 seconds]
--- Log closed Wed May 20 00:00:26 2020