--- Log opened Mon Sep 21 00:00:24 2020
00:05 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
00:07 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning
00:22 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
00:22 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
00:51 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection]
01:03 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning
01:26 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Ping timeout: 240 seconds]
01:27 -!- darosior [~darosior@194.36.189.246] has quit [Ping timeout: 256 seconds]
01:29 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning
01:52 -!- lxer [~lx@81-206-142-46.pool.kielnet.net] has joined #c-lightning
02:17 -!- darosior3 [~darosior@194.36.189.246] has joined #c-lightning
02:22 -!- darosior3 [~darosior@194.36.189.246] has quit [Quit: ya vps net disruption]
03:05 -!- darosior [~darosior@194.36.189.246] has joined #c-lightning
03:05 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
03:10 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
03:11 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
03:26 < rusty> cdecker: https://github.com/ElementsProject/lightning/pull/4071 there youj go...
03:26 <@cdecker> Thanks rusty, will review now
03:35 < rusty> cdecker: also worried about the nomenclature for this "notify" feature.  We already use "notifications" for plugin notifications; should we use another name like "update" for these?
03:36 <@cdecker> Yeah, might get confusing over time, `cmdstatus` might be another option
03:37 <@cdecker> Or we can sidestep all of this and call it `cmd{cmd_id}`, so it disambiguates in the notification name rather than by peeking into the payload
03:51 < rusty> Hmm... I've already got methods "progress" and "message" defined for separate species of notifications
03:53 <@cdecker> Ah, the pain of naming things
03:53 <@cdecker> :-)
04:01 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 272 seconds]
04:23 < rusty> cdecker: but I just got PROGRESS BARS working in lightning-cli! :)
04:23 <@cdecker> Wow fancy, what kind of progress are they showing?
04:24 < rusty> cdecker: dummy module:
04:25 < rusty> But now I can demo at meeting... if I can figure out how to share screen in Jitsi!
04:27 <@cdecker> Excellen 👍
04:28 <@cdecker> I finally went through sentry and fixed a couple of tests that were being rerun a bit too often for my taste
04:28 < m-schmoock> rusty: theres a butto on the bottom left for sharing ususally
04:28 < m-schmoock> btw I got my micro working ;)
04:28 < rusty> m-schmoock: yeah, I just tested, seems to work...
04:28 < rusty> m-schmoock: excellent!  Looking fwd to it!
04:28 < m-schmoock> my new laptop does not have audio routing issues
04:29 <@cdecker> Definitely looking forward to the meeting today ^^
04:29 < m-schmoock> the other one was a replacement because I drowned coffee in my laptop
04:29 < m-schmoock> also, the new one is able to run all python tests in under 4 minutes :D
04:29 < m-schmoock> (w/o Valgrind)
04:30 <@cdecker> What? 4 minutes for a `make pytest` run? That's insane
04:34 < m-schmoock> Yes, using PYTEST_PAR 32 and DEVELOPER 1  on an i9 mobile something fast 8 cores 61ht
04:34 < m-schmoock> last time I checked 3mins58 
04:34 < m-schmoock> *16 ht
04:35 < m-schmoock> let me check with valgrind :D 
04:35 < m-schmoock> make full-check   actually
04:50 -!- lxer [~lx@81-206-142-46.pool.kielnet.net] has quit [Ping timeout: 240 seconds]
04:53 <@cdecker> Ok, I need one of those machines
05:02 < m-schmoock> just make pycheck takes ~ 3m30s
05:02 < m-schmoock> quite nice
05:03 < m-schmoock> doing some tests with differen PYTEST_PAR values and valgrind
05:04 < m-schmoock> for a mobile CPU this is good. desktops are faster for sure, are they?
05:04 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
05:15 <@cdecker> lol, 21 minutes on my machine :-)
05:15 <@cdecker> I mostly offload to GCP for parallel testing, so it's not that bad actually
05:15  * rusty tests his AMD Ryzen Threadripper 2950X 16-Core Processor
05:20 < rusty> m-schmoock: ... 4m12.605s (though over ssh via a machine in Singapore,and I did get a spurious test failure)
05:26 < m-schmoock> hmmm. dunno, the Ryzen 2950X should be faster than i9-10885H mobile.
05:27 < m-schmoock> the i9 takes 3m30 - 3m45 depending on what I do in the background. just DEVELOPER=1 PYTEST_PAR=24 (seems better tha 32) and no valgrind of course
05:27 < m-schmoock> i9 is beast ^^
05:28 < m-schmoock> (no exp features)
05:28 < rusty> Yes, it definitely should!  
05:28 < m-schmoock> what settings do you use?
05:29 < rusty> That was 'time make -C lightning-ltest -j32 full-check VALGRIND=0 PYTEST_PAR=32' on a developer build.
05:30 < rusty> I previously found PYTEST_PAR=12 better, but then we have sped up our tests...
05:31 < m-schmoock> I used to test by  'time make -j16 pytest PYTEST_PAR=24 DEVELOPER=1' on master sources
05:36 < m-schmoock> all green real 3m44.579s
05:36 < m-schmoock> I cant complain _D
05:50 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
06:04 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Ping timeout: 240 seconds]
06:38 -!- lxer [~lx@81-206-142-46.pool.kielnet.net] has joined #c-lightning
07:31 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning
08:13 -!- polydin [~george@rrcs-71-78-170-67.sw.biz.rr.com] has joined #c-lightning
08:32 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
08:32 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
09:12 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 2.9]
09:18 -!- lxer [~lx@81-206-142-46.pool.kielnet.net] has quit [Ping timeout: 240 seconds]
09:23 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
09:42 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Quit: Leaving]
09:42 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
10:30 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
11:17 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
11:18 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
11:39 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds]
11:39 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
11:42 -!- lxer [~lx@ip5f5bf473.dynamic.kabel-deutschland.de] has joined #c-lightning
11:44 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Ping timeout: 240 seconds]
11:56 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
12:00  * jasan sounds a soft bell -- one more hour to meeting
12:01 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Remote host closed the connection]
12:02 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning
12:02 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
12:03 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
12:17 < jasan> by the way, I suggest everyone to test their connection using dslreports.com/speedtest which measures a very important value Bufferbloat
12:18 < jasan> for more info: https://www.bufferbloat.net
12:22 < jasan> here you can see my test where I got A for Bufferbloat (thanks sch_cake Linux module I use on the router; without it it was more like C or even D).
12:22 < jasan> http://www.dslreports.com/speedtest/65674761
12:38 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 265 seconds]
12:39 < jasan> I just watched the Rusty's Getting Started webinar and recommend it to all newcommers (note it takes one hour to watch).
12:41 < jasan> https://youtu.be/fab4P3BIZxk
12:41 <@cdecker> jasan: just tested it and over WLAN I get 100ms bufferbloat, on whire 3ms xD
12:42 < jasan> cdecker: thanks for checking
12:56 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
12:56 < jasan> Good morning, Rusty!
12:57 < rusty> Hello all!
12:57 < m-schmoock> -QQQQ°_°
12:59 < rusty> https://meet.jit.si/CLightning-Open-Meeting if you want video and audio in all its glory!
13:12 -!- polydin [~george@rrcs-71-78-170-67.sw.biz.rr.com] has quit [Remote host closed the connection]
13:14 -!- polydin [~george@rrcs-71-78-170-67.sw.biz.rr.com] has joined #c-lightning
13:25 -!- kexkey [~kexkey@89.36.78.166] has joined #c-lightning
14:01 < rusty> Thanks, that was fun!
14:01 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
14:01 < m-schmoock> yep. meeting minutes: reduce log buffer, log_broken on duplicated close_to
14:03 < m-schmoock> and Note to myself: check if given state is recent
14:03 < m-schmoock> gn8 cu
14:03 < lxer> 👍
14:08 -!- polydin [~george@rrcs-71-78-170-67.sw.biz.rr.com] has quit [Remote host closed the connection]
15:10 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
15:11 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
15:52 -!- polydin [~george@rrcs-71-78-170-67.sw.biz.rr.com] has joined #c-lightning
15:55 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection]
16:15 -!- polydin [~george@rrcs-71-78-170-67.sw.biz.rr.com] has quit [Ping timeout: 272 seconds]
16:22 -!- lxer [~lx@ip5f5bf473.dynamic.kabel-deutschland.de] has quit [Ping timeout: 265 seconds]
17:00 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
17:00 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
18:32 -!- polydin [~george@rrcs-71-78-170-67.sw.biz.rr.com] has joined #c-lightning
19:03 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
19:18 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has left #c-lightning []
19:51 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 272 seconds]
20:49 -!- polydin [~george@rrcs-71-78-170-67.sw.biz.rr.com] has quit [Ping timeout: 240 seconds]
22:07 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
23:39 -!- reallll [~belcher@unaffiliated/belcher] has joined #c-lightning
23:43 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 264 seconds]
23:53 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
23:54 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
23:59 -!- reallll is now known as belcher
--- Log closed Tue Sep 22 00:00:25 2020