--- Log opened Mon Jan 17 00:00:32 2022
01:03 -!- jonatack [jonatack@user/jonatack] has quit [Quit: Connection closed]
01:45 -!- jonatack [jonatack@user/jonatack] has joined #c-lightning
02:04 -!- kexkey [~kexkey@static-198-54-132-171.cust.tzulo.com] has quit [Ping timeout: 240 seconds]
02:06 -!- kexkey [~kexkey@static-198-54-132-123.cust.tzulo.com] has joined #c-lightning
05:05 -!- bitdex_ [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
05:07 < cdecker[m]> Very interesting, might be a coincidence though since we aren't IO bound (mostly latencies with peers impacting throughput afaik)
05:24 -!- jespada [~jespada@87.74.36.188] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
05:58 -!- jb55 [~jb55@user/jb55] has joined #c-lightning
07:25 < vincenzopalazzo> cdecker: I have a unrelated question about the changelog generation, do you use internal tools to generate it or there is some open source project to do it?
07:29 < cdecker[m]> It's a very simple script in `devtools/changelog.py`
07:30 < vincenzopalazzo> ops I missed it in the devtools :) So simple that there is any tools in github action graph some patter from command line :) Thanks I will look into it
07:40 < grubman> hm what is the proper way to shut down lightningd if lightning-cli is unresponsive?
07:41 < vincenzopalazzo> grubman: what is mean unresponsive? there is any plugin that you are running?
07:41 < grubman> just clboss
07:41 < grubman> unresponsive as in it hangs indefinitely 
07:41 -!- jespada [~jespada@87.74.36.188] has joined #c-lightning
07:42 < vincenzopalazzo> killing lightningd process could be not a good idea if lightningd are writing on db can cause problem
07:42 < vincenzopalazzo> Mh, I think that this is a little bit strange!
07:44 < grubman> i've also encountered that infinite "peer transient failure" reconnect loop 
07:44 < grubman> not sure if related
08:27 < cdecker[m]> No, killing lightningd should always be safe: sqlite3 should be able to rollback a transaction that was interrupted, and we always commit the DB transaction flushing to disk before doing anything that might be risky. This is part of our guarantee, since we can't ask users not to ki accidentally (battery low, kernel panic, etc)
08:28 < cdecker[m]> Which lightning-cli call was hanging? Some calls are synchronous and will only return after they complete. Also looking at the logs might give an indication where things are at the moment
08:30 < mschmoock> cdecker[m]: I updated #4864 addressing rustys issues and left a comment. https://github.com/ElementsProject/lightning/pull/4864#issuecomment-1011961719   
08:31 < mschmoock> Its better now, but results in a lot of #include wireadd.h and base32.h. therefore I suggest to decouple wireaddr and wireaddr_internal
09:10 < grubman> cdecker[m]: okay thanks for the reply. re: hanging call, basically any call hangs. e.g. getinfo, listpeers, etc.
09:10 < cdecker[m]> Thanks mschmoock ^^
09:10 < cdecker[m]> grubman: that's very strange indeed. Is this right from the start, or does it occur after running ok for a while?
09:15 < grubman> after running ok for a while
09:17 < grubman> i killed lightningd. restarting it and seeing what happens.
11:33 -!- yakshaver123 is now known as yakshaver
11:55 -!- jarthur [~jarthur@2603-8080-1540-002d-8926-a20e-7ef6-caff.res6.spectrum.com] has joined #c-lightning
12:19 -!- kexkey [~kexkey@static-198-54-132-123.cust.tzulo.com] has quit [Ping timeout: 250 seconds]
12:33 -!- kexkey [~kexkey@89.36.78.203] has joined #c-lightning
12:44 -!- kexkey [~kexkey@89.36.78.203] has quit [Ping timeout: 256 seconds]
12:44 -!- kexkey [~kexkey@37.120.205.219] has joined #c-lightning
14:16 -!- kexkey [~kexkey@37.120.205.219] has quit [Ping timeout: 250 seconds]
14:26 -!- kexkey [~kexkey@89.36.78.10] has joined #c-lightning
15:02 -!- jb55 [~jb55@user/jb55] has quit [Ping timeout: 250 seconds]
16:15 -!- jb55 [~jb55@user/jb55] has joined #c-lightning
16:28 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
16:35 -!- sr_gi [~sr_gi@47.61.62.163] has quit [Read error: Connection reset by peer]
16:35 -!- sr_gi [~sr_gi@47.61.62.163] has joined #c-lightning
16:36 -!- kakolainen[m] [~kakolaine@2001:470:69fc:105::34f9] has quit [Ping timeout: 268 seconds]
16:36 -!- vincenzopalazzo [~vincenzop@2001:470:69fc:105::a67] has quit [Ping timeout: 268 seconds]
16:36 -!- kon[m]1 [~konnixbit@2001:470:69fc:105::b9af] has quit [Ping timeout: 268 seconds]
16:39 -!- kakolainen[m] [~kakolaine@2001:470:69fc:105::34f9] has joined #c-lightning
16:41 -!- vincenzopalazzo [~vincenzop@2001:470:69fc:105::a67] has joined #c-lightning
16:45 -!- kon[m]1 [~konnixbit@2001:470:69fc:105::b9af] has joined #c-lightning
17:56 -!- jb55 [~jb55@user/jb55] has quit [Ping timeout: 240 seconds]
18:28 -!- jb55 [~jb55@user/jb55] has joined #c-lightning
18:54 -!- jarthur [~jarthur@2603-8080-1540-002d-8926-a20e-7ef6-caff.res6.spectrum.com] has quit [Ping timeout: 240 seconds]
18:57 -!- jarthur [~jarthur@2603-8080-1540-002d-8926-a20e-7ef6-caff.res6.spectrum.com] has joined #c-lightning
19:01 -!- jb55 [~jb55@user/jb55] has quit [Ping timeout: 256 seconds]
19:49 -!- jarthur_ [~jarthur@2603-8080-1540-002d-c475-c516-38bc-5933.res6.spectrum.com] has joined #c-lightning
19:49 -!- jarthur [~jarthur@2603-8080-1540-002d-8926-a20e-7ef6-caff.res6.spectrum.com] has quit [Ping timeout: 240 seconds]
20:59 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
21:00 -!- jb55 [~jb55@user/jb55] has joined #c-lightning
21:01 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
21:01 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Client Quit]
21:01 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
21:43 -!- jb55 [~jb55@user/jb55] has quit [Ping timeout: 268 seconds]
--- Log closed Tue Jan 18 00:00:33 2022