--- Log opened Wed Aug 05 00:00:40 2020 00:25 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 00:29 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 260 seconds] 00:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 00:48 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 00:54 -!- dr-orlovsky [~dr-orlovs@194.230.155.142] has joined #c-lightning 01:24 -!- dr-orlovsky [~dr-orlovs@194.230.155.142] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 01:32 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 01:32 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 02:39 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds] 03:41 <@cdecker> I'm a bit late to the party but we clamp the number of initial parts to 1/3rd of the number of locally available HTLCs across all our channels (sum the max number of HTLCs we can add, subtract the number of HTLCs we already have) 03:42 <@cdecker> So what we end up doing for the first payment we start off with 1/3rd, then have some in flight when the second concurrent payment starts, and it can also take 1/3rd of the remaining HTLCs and so on 03:43 <@cdecker> They might end up exhausting HTLCs we can add to channels if we adaptively split and have other concurrent payments as well, but 10ksat has a relatively reasonable chance of not requiring splits (according to my measurements 83% of 10ksat parts will succeed in less than 10 attempts) 03:44 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack] 03:55 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 03:59 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 03:59 -!- vasild_ is now known as vasild 04:42 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds] 04:59 < darosior> My `pay` just crashed on `listpays` :-( 05:02 < darosior> And now it's happy (not much more logs than `2020-08-05T11:56:24.841Z INFO plugin-pay: Killing plugin: Plugin exited before completing handshake.` for the crash, and i don't run with io-level logging) 05:03 < darosior> However fwiw i previously just paid a tiny invoice using routehints and mpp, went perfectly well 05:19 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning 05:30 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning 05:35 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack] 05:41 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning 05:54 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 256 seconds] 05:57 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 06:23 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 07:00 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 07:02 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection] 07:02 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 07:30 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 07:51 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-xadswhvwruqyrqgr] has left #c-lightning [] 07:51 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-xadswhvwruqyrqgr] has joined #c-lightning 08:21 <@cdecker> Hm, that's weird, `pay` shouldn't be doing anything on startup, so the handshake thing is new 08:35 < darosior> I think we give this error when a plugin crash during a proxied RPC call to it (not 100% sure though) 08:35 < darosior> So not on startup 08:36 < darosior> Yeah, checked and we say that on the tal destructor so even when the plugin is dead 08:58 <@cdecker> Any traceback on `listpays`? 09:23 < darosior> That's why i said above: no backtrace in the logs, just lightningd telling me `pay`died (should have ran with io :/) 10:09 <@cdecker> Interesting, that'd point towards the plugin terminating with `plugin_err` which exits cleanly with a message. You could look at what the last output line was 10:26 -!- rafalcpp [~racalcppp@ip-178-214.ists.pl] has quit [Ping timeout: 265 seconds] 10:39 -!- rafalcpp [~racalcppp@ip-178-214.ists.pl] has joined #c-lightning 10:42 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 11:05 -!- rafalcpp [~racalcppp@ip-178-214.ists.pl] has quit [Ping timeout: 256 seconds] 11:19 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 11:36 < roasbeef> interesting, what we've shipped w/ so far is basically on the opposite end of the spectrum, with a flag that lets the user set the # of max splits: it only splits when it has no other choice, but looking to add some slightly more aggressive heuristics 11:44 < roasbeef> would seem there's also a tradeoff beign made for smaller split w.r.t total fee paid, since each split accmulates w/e base fee across each channel traversed, fee rates are still pretty slow generally, so that factor may dominate depending on the route compared to a larger fewer set of splits 12:42 <@cdecker> I have a blog post queued about our experience implementing MPP, I'll post it here as soon as it's public as well 13:02 -!- sr_gi [~sr_gi@static-144-88-225-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer] 13:02 -!- sr_gi [~sr_gi@static-144-88-225-77.ipcom.comunitel.net] has joined #c-lightning 13:14 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 13:15 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 13:19 -!- cubancorona [~cubancoro@pool-72-77-31-161.pitbpa.ftas.verizon.net] has joined #c-lightning 13:19 -!- cubancorona [~cubancoro@pool-72-77-31-161.pitbpa.ftas.verizon.net] has left #c-lightning [] 13:28 -!- rafalcpp [~racalcppp@ip-178-214.ists.pl] has joined #c-lightning 14:53 -!- rafalcpp [~racalcppp@ip-178-214.ists.pl] has quit [Read error: Connection reset by peer] 14:58 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 265 seconds] 15:55 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 15:58 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 15:58 -!- vasild_ is now known as vasild 15:59 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-xadswhvwruqyrqgr] has left #c-lightning [] 15:59 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-xadswhvwruqyrqgr] has joined #c-lightning 16:13 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection] 16:20 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 16:22 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 16:37 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 16:40 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 17:02 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Quit: Leaving] 17:03 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 17:09 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection] 17:28 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 17:54 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Ping timeout: 240 seconds] 17:56 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning 18:23 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 18:23 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 18:39 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection] 18:58 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning 18:59 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection] 19:17 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 19:45 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds] 20:05 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Ping timeout: 240 seconds] 20:06 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning 20:14 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection] 20:14 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning 21:05 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 240 seconds] 21:20 -!- k3tan [~pi@unaffiliated/k3tan] has joined #c-lightning 22:24 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 22:25 < zmnscpxj__> Found a bug in our MPP: https://github.com/ElementsProject/lightning/pull/3908 22:53 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 23:17 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 240 seconds] 23:18 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 23:21 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds] 23:24 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 260 seconds] 23:29 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning --- Log closed Thu Aug 06 00:00:41 2020