--- Log opened Fri Sep 03 00:00:56 2021
00:55 < mschmoock> niftynei: thx. I should have known
00:56 < mschmoock> so the problem comes not particular from the delay, but by registering other hooks that do stuff we overlap with the db_write which is really bad
00:58 < mschmoock> yes, just retried, having no delay in db_write but stuff on other hoooks also does this
00:58 < mschmoock> we could have a failsafe for that in lightingd plugin handler
01:19 -!- AdityaSharma[m] [~M1adityam@2001:470:69fc:105::c473] has quit [Ping timeout: 252 seconds]
01:22 -!- kon[m] [~konnixbit@2001:470:69fc:105::b9af] has quit [Ping timeout: 252 seconds]
01:22 -!- ksedgwic [~ksedgwicm@2001:470:69fc:105::ce1] has quit [Ping timeout: 252 seconds]
01:24 -!- AdityaSharma[m] [~M1adityam@2001:470:69fc:105::c473] has joined #c-lightning
01:29 < nathanael> i noticed having two 'num_pending_channels' but can't see anything with 'listpeers' - any way to find out more about these two pending channels?
01:32 -!- ksedgwic [~ksedgwicm@2001:470:69fc:105::ce1] has joined #c-lightning
01:35 -!- kon[m] [~konnixbit@2001:470:69fc:105::b9af] has joined #c-lightning
02:34 -!- kakolainen[m] [~kakolaine@2001:470:69fc:105::34f9] has quit [Ping timeout: 245 seconds]
02:34 -!- kakolainen[m] [~kakolaine@2001:470:69fc:105::34f9] has joined #c-lightning
03:05 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
03:27 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
03:43 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 240 seconds]
04:15 < mschmoock> nathanael: thats strange, listpeers should show pending channels afaik
04:18 < nathanael> yeah thought so too
04:21 < nathanael> also just noticed: 'getinfo' shows 21 peers and '-F listpeers' only 'peers[20]'
06:52 -!- jasan [~j@tunnel625336-pt.tunnel.tserv1.bud1.ipv6.he.net] has quit [Quit: jasan]
06:56 < mschmoock> Question to the adience: Is the `commitment_revocation` hook lacking information like channel_id and maybe peer_id etc?
06:58 < mschmoock> currently it only holds tx and txid. but what would a plugin do with that if it doesnt know which channel that belongs to?
06:59 < mschmoock> will open a PR... I cant find a reason why this data is hidden to the plugins
07:31 < mschmoock> done:  https://github.com/ElementsProject/lightning/pull/4760 
08:10 -!- valwal [~valwal@96.224.58.144] has quit [Ping timeout: 252 seconds]
09:16 -!- Victorsueca [~Victorsue@90.165.120.190] has joined #c-lightning
09:40 < mschmoock> feature in 40 minutes... :D
09:40 < mschmoock> (small feature though)
09:41 < mschmoock> tests seem green, all we need is an ACK
09:50 < ufotofu> i'm getting that pending-channel-but-listpeers-not-reflecting-it issue too
09:50 < ufotofu> on v0.10.1
09:54 < mschmoock> oO
10:17 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: Client closed]
10:18 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
10:43 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 256 seconds]
11:10 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
11:13 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
11:14 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 276 seconds]
11:21 -!- mschmoock [~will@schmoock.net] has quit [Ping timeout: 240 seconds]
11:21 -!- mschmoock [~will@schmoock.net] has joined #c-lightning
11:21 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 276 seconds]
11:22 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 276 seconds]
11:22 -!- aechu [~major@gateway/tor-sasl/major] has quit [Ping timeout: 276 seconds]
11:29 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
11:29 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning
11:29 -!- aechu [~major@gateway/tor-sasl/major] has joined #c-lightning
12:29 -!- belcher [~belcher@user/belcher] has quit [Quit: Leaving]
12:54 -!- Guest60 [~Guest60@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
13:17 -!- ufotofu [~ufotofu@user/ufotofu] has quit [Ping timeout: 240 seconds]
13:55 -!- yakshaver123 is now known as yakshaver
15:01 -!- Guest60 [~Guest60@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Quit: Client closed]
16:21 -!- belcher [~belcher@user/belcher] has joined #c-lightning
17:00 -!- Netsplit *.net <-> *.split quits: jarthur, mschmoock, Victorsueca, k3tan
17:00 -!- Netsplit over, joins: mschmoock
17:02 -!- k3tan [~pi@user/k3tan] has joined #c-lightning
17:07 -!- jarthur [~jarthur@2603-8080-1540-002d-4d20-c6a4-d08c-1eac.res6.spectrum.com] has joined #c-lightning
17:16 -!- belcher_ [~belcher@user/belcher] has joined #c-lightning
17:19 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 240 seconds]
18:50 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning
19:51 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
21:34 -!- jarthur [~jarthur@2603-8080-1540-002d-4d20-c6a4-d08c-1eac.res6.spectrum.com] has quit [Ping timeout: 240 seconds]
21:37 -!- jarthur [~jarthur@2603-8080-1540-002d-00fd-de4a-ab18-4740.res6.spectrum.com] has joined #c-lightning
21:42 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 276 seconds]
22:18 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
23:02 -!- rusty [~rusty@103.93.169.121] has quit [Quit: Leaving.]
23:02 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
23:06 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 252 seconds]
23:12 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
23:24 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 252 seconds]
--- Log closed Sat Sep 04 00:00:57 2021