--- Log opened Tue Dec 17 00:00:40 2019
00:15 < m-schmoock> t0mix: is your node Jublie or was this gallizoli ?
00:16 < m-schmoock> nah, your is also named t0mix. sry
00:34 -!- orlovsky [~dr-orlovs@194.230.155.171] has quit [Quit: Textual IRC Client: www.textualapp.com]
00:34 -!- dr-orlovsky [~dr-orlovs@194.230.155.171] has joined #c-lightning
01:03 -!- masterdonx2 [~masterdon@45.9.250.100] has joined #c-lightning
01:05 -!- potatoe_1ace [~potatoe_f@157.230.27.253] has joined #c-lightning
01:09 -!- somethinglittle [~nothingmu@unaffiliated/nothingmuch] has joined #c-lightning
01:09 -!- warren_ [~warren@fedora/wombat/warren] has joined #c-lightning
01:09 -!- sword_smith [sword_smit@bitcoinfundamentals.org] has quit [Disconnected by services]
01:10 < darosior> Yeah Jubilee is gallizoltan's
01:10 -!- Netsplit *.net <-> *.split quits: instagibbs, belcher, MasterdonX, warren, potatoe_face, fiatjaf
01:11 -!- Netsplit *.net <-> *.split quits: nothingmuch, raucao, @cdecker, blockstream_bot
01:11 -!- Netsplit over, joins: instagibbs
01:13 -!- raucao [~raucao@skippe2.nine.ch] has joined #c-lightning
01:13 < darosior> fiatjaf: same structure
01:14 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
01:19 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
01:21 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
01:37 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
01:38 < m-schmoock> darosior: I send him a message, his node crashes when trying to route payments :D
01:40 < darosior> m-schmoock: Ah! I wondered why I had difficulties rebalancing through his node x)
01:40 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 260 seconds]
01:44 < darosior> vasild: "even better, I guess then it will be trivial to write a direct-to-bitcoind-over-tcp-instead-of-exec-bitcoin-cli plugin" => Yeah even if I'm really not sure about using non-locally RPC. I plan to do one for core's REST interface too :p (even if it would maybe means txindex mandatory, which rusty and cdecker have been carefull in not needing
01:44 < darosior> since the begining)
02:10 < vasild> darosior: What do you mean by "not sure about using non-locally RPC"? That using a bitcoind which is on another machine could cause some problems?
02:11 < darosior> via RPC, yes. I don't think exposing RPC is a good idea
02:12 < vasild> ok, but then this can also happen now - bitcoin-cli could be configured to connect to != 127.0.0.1
02:27 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
02:32 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
02:33 < vasild> anyway - my immediate problem is that sending SIGHUP to lightningd causes its bitcoin-cli to quit, causing lightningd itself to quit. I am not sure if this is widespread or something in my environment. Maybe the signal propagation can be suppressed somehow, I haven't investigated it.
03:00 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
03:04 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Quit: leaving]
03:04 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
03:32 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 248 seconds]
03:36 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning
04:02 < darosior> "bitcoin-cli could be configured to connect to != 127.0.0.1" => yes
04:13 -!- vincenzopalazzo [~vincenzop@2.226.158.237] has joined #c-lightning
04:21 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 252 seconds]
04:33 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning
04:43 -!- jonatack [~jon@213.152.161.117] has joined #c-lightning
04:59 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 246 seconds]
05:00 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning
05:45 -!- somethinglittle is now known as nothingmuch
06:19 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
06:33 -!- jonatack [~jon@213.152.161.117] has quit [Ping timeout: 245 seconds]
07:00 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
07:00 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
07:12 < willcl_ark> Would there be any resistance to  modifying `lightningd/plugin.c:plugin_kill` so that it issues a SIGTERM & checks if PID killed before a final SIGKILL if necessary? This would allow for better plugin cleanup.
07:39 < darosior> willcl_ark: Why not, but a stop command would be even better
07:47 -!- vincenzopalazzo [~vincenzop@2.226.158.237] has quit [Remote host closed the connection]
07:55 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
08:29 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
08:32 -!- alko89 [~alko@cpe-85-10-28-138.static.amis.net] has quit [Quit: Konversation terminated!]
08:51 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection]
08:52 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #c-lightning
08:54 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 2.6]
08:58 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
09:34 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 265 seconds]
09:43 -!- niftynei 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.8.0 **FUNDS AT RISK IF < 0.7.1!** Logs at http://gnusha.org/c-lightning/
09:43 <@niftynei> done m-schmoock 
10:00 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning
10:22 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
10:22 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
10:23 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning
10:30 -!- k3tan [k3tan@gateway/vpn/protonvpn/k3tan] has quit [Remote host closed the connection]
10:31 < shesek> when using lightning-cli with an explicit --rpc-file, what does it use --lightning-dir and --network for, if at all?
10:35 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 245 seconds]
10:39 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning
10:44 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 248 seconds]
11:24 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Ping timeout: 248 seconds]
11:29 -!- achow101 [~achow101@unaffiliated/achow101] has joined #c-lightning
11:35 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Ping timeout: 268 seconds]
11:38 -!- achow101 [~achow101@unaffiliated/achow101] has joined #c-lightning
12:37 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:806a:4e5:5581:b0ff] has joined #c-lightning
12:49 -!- alko89 [~alko@cpe-85-10-28-138.static.amis.net] has joined #c-lightning
12:52 < fiatjaf_> https://lightning.readthedocs.io/PLUGINS.html#htlc-accepted what is the structure for "onion" when the type is "TLV"?
12:52 < fiatjaf_> is it like {T: V}? just taking each field and writing it as a key in the JSON object?
12:59 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:806a:4e5:5581:b0ff] has quit [Ping timeout: 246 seconds]
13:02 < darosior> shesek: there is a precedence, IIRC
13:02 < darosior> fiatjaf_: I've already answered above
13:40 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 260 seconds]
13:42 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
14:21 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning
14:24 < shesek> darosior, I got disconnected earlier and missed your message, saw it now on gnusha.org. the problem is that lightning-cli still wants the lightning-dir and network to be valid (its trying to move into it and fails) even when rpc-file is provided
14:24 < shesek> I sent a second message that seemed to drop when I got disconnected: <shesek> or, more to the point: I have a unix rpc socket at a known location, but I don't know which network its for. how can I issue rpc commands against it with lightning-cli? it appears to refuse to work with --rpc-file but without a valid --lightning-dir and --network, but it doesn't seem like it really needs it for anything
14:26 < darosior> shesek: Ah, I think that's part of the last change which merged the conf options of lightningd and lightning-cli..
14:26 < shesek> it is a new behavior since 0.8, but I think its related to c-lightning using subdirectories now
14:27 < darosior> Yeah that's part of the same change
14:27 < darosior> I'm giving it a look
14:27 < shesek> it expects to find lightning-rpc inside <lightning-dir>/<network>, and can't be told not to look into the <network> subdirectory and just grab the lightning-rpc inside lightning-dir
14:27 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 248 seconds]
14:28 < shesek> or just use the explicit rpc-file and ignore the other options
14:30 < darosior> shesek: Could you open an issue so that we don"t forget ?
14:30 < shesek> yes, will do
14:30 < darosior> Thanks!
14:36 < shesek> to give some more background, I ran into this with spark which currently expects users to specify the path to the directory containing lightning-rpc and does not require them to specify the network. i.e. `spark-wallet --ln-path ~/.lightning` for 0.7, or now `--ln-path ~/.lightning/regtest` for 0.8. this works, as long as I don't need to use lightning-cli.
14:37 < shesek> in the docker environment however, my entrypoint script does need to use lightning-cli, and it seems like the only way to do this is to require users to provide an explicit configuration option with the network name and mount the base data directory into the container instead of mounting the network subdirectory. which feels needlessly more complicated than just mounting the network subdirectory directly...
14:38 < shesek> this basically translates to `-v ~/.lightning:/etc/lightning -e NETWORK=regtest` vs `-v ~/.lightning/regtest:/etc/lightning` 
14:50 < shesek> https://github.com/ElementsProject/lightning/issues/3352
14:52 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
14:57 -!- alko89 [~alko@cpe-85-10-28-138.static.amis.net] has quit [Remote host closed the connection]
15:00 -!- orlovsky [~dr-orlovs@194.230.155.171] has joined #c-lightning
15:01 < darosior> Patch's on its way :)
15:01 < shesek> awesome :-)
15:01 -!- dr-orlovsky [~dr-orlovs@194.230.155.171] has quit [Ping timeout: 248 seconds]
15:02 < shesek> looks like I'm able to `mkdir /tmp/dummy /tmp/dummy/bitcoin` and run `lightning-cli --rpc-file /patho/to/socket --lightning-dir /tmp/dummy`, so I guess that answers the question on whether they're really needed for anything
15:03 < shesek> "patch on its way" answered that too of course :)
15:05 < darosior> Actually I think I'm just gonna be deleted the chdir into lightning-dir which seems superfluous, (rusty: ping for when you connect)
15:06 < shesek> looks like I might actually have to do this /tmp/dummy hack to support v0.8.0 without requiring users to provide additional configurations >_<
15:06 < darosior> ^^
15:17 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
15:17 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
15:18 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning
15:31 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
15:46 -!- cubancorona [~cubancoro@pool-72-77-31-161.pitbpa.ftas.verizon.net] has quit [Quit: Leaving]
15:54 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
16:05 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 265 seconds]
16:39 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
16:39 -!- Netsplit *.net <-> *.split quits: dmkathayat
16:39 -!- Netsplit over, joins: dmkathayat
16:43 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Client Quit]
16:51 < fiatjaf_> what happens with htlc_accepted in case of a MPP?
16:54 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 260 seconds]
17:13 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
17:21 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
17:50 < shesek> darosior, just a wild guess, but perhaps the chdir was needed to resolve the path of lightning-rpc as relative to the data dir?
18:50 < shesek> appears like that's indeed the case, I tried this locally with your branch
21:17 < rusty> darosior: off the top of my head, the only thing lightning-cli cares about the config for is to locate rpc-filename.  Perhaps if --rpc-filename is used, we shouldn't even read the config?
21:18 < rusty> darosior: otherwise, if we don't chdir, I worry about other things.  Like 'rpc-filename' in a config is relative to the network dir IIRC, and 'include' in config files is...
22:12 -!- kabaum [~kabaum@2001:9b1:efd:9b00::281] has quit [Ping timeout: 250 seconds]
22:32 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
22:32 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
22:34 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 260 seconds]
22:41 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
22:50 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
22:50 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
23:04 -!- k3tan [k3tan@gateway/vpn/protonvpn/k3tan] has joined #c-lightning
23:19 -!- kabaum [~kabaum@185.224.57.161] has joined #c-lightning
23:27 -!- kabaum [~kabaum@185.224.57.161] has quit [Ping timeout: 258 seconds]
23:35 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
23:35 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
23:44 -!- kabaum [~kabaum@185.224.57.161] has joined #c-lightning
--- Log closed Wed Dec 18 00:00:40 2019