--- Log opened Mon Feb 18 00:00:53 2019 00:56 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection] 01:09 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning 01:20 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving] 01:22 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning 01:42 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 01:42 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Remote host closed the connection] 01:44 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 01:55 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 250 seconds] 01:59 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 02:03 -!- kexkey [~kexkey@87.101.92.74] has quit [Read error: Connection reset by peer] 02:13 < m-schmoock> cdecker: are the DocBook XML templates for the generated manpages somewhere accessible? 02:24 -!- harding [~quassel@li1258-130.members.linode.com] has quit [Ping timeout: 250 seconds] 02:38 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 02:45 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 02:47 -!- harding [~quassel@li1258-130.members.linode.com] has joined #c-lightning 03:06 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 03:39 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 05:14 <@cdecker> jonasschnelli: that's a known bug that is fixed in master 05:14 <@cdecker> m-schmoock: didn't have a lot to do with the manpages 05:32 < fiatjaf> does decodepay check the signature? 05:33 < fiatjaf> can I pay expired invoices? is there a setting to force that? 06:12 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection] 06:54 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 06:59 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 07:52 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 07:53 -!- kexkey [~kexkey@87.101.92.74] has joined #c-lightning 08:23 -!- booyah_ [~bb@193.25.1.157] has joined #c-lightning 08:24 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 08:26 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 255 seconds] 08:28 -!- kexkey [~kexkey@87.101.92.74] has quit [Ping timeout: 246 seconds] 09:13 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving] 10:09 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning 10:24 < jonasschnelli> cdecker: Oh. I thought I'm running master... (3e4a3bafc3db443c00a1bb16f95c0f0ca69850d4 / Fri Feb 8) 10:25 < jonasschnelli> ah. maybe a405c22fc9cffbe2a6c27a0a877db63224599817 fixes it 10:32 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 10:42 <@cdecker> jonasschnelli: no, that's a separate issue, lemme dig up the actual fix 10:43 <@cdecker> This is it: https://github.com/ElementsProject/lightning/pull/2268 10:43 <@cdecker> Uhm, but if you compiled on Feb 8, then you should have that fix 10:43 < jonasschnelli> Could be that I has feb 8th as source tree but not compiled... but unlikely. 10:44 < jonasschnelli> I'll have an eye on it now that I run master from feb 18th 10:50 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning 10:53 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 10:54 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 11:33 <@cdecker> :+1: 11:42 -!- Kostenko [~Kostenko@bl5-167-188.dsl.telepac.pt] has quit [Remote host closed the connection] 12:26 -!- kexkey [~kexkey@87.101.92.74] has joined #c-lightning 13:01 < t0mix> is lnd faster than c-lightning when issuing "pay" ? it looks so based on observation. any experience with both anyone? 13:02 < t0mix> when I am paying invoice, it takes 10-20 seconds to be paid. .. but when receiving payment (e.g. from spinwheel), payments is sent within 1-2 seconds. 13:02 < t0mix> I think they use LND. but I don't know if that's the reason. 13:08 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 245 seconds] 13:12 < m-schmoock> cdecker: I have some open questions regarding the setchannelfee feature. have a look at PR 2342: 1. Am I so supposed to do min/max constrain checks? Probably yes, but which exactly? 2. Can I set the channel fees also in other state than CHANNELD_NORMAL? 3. Is it okay, to disable the feature and restore global values when leaving out base & ppm values? 4. Should it be allowed to set the 13:12 < m-schmoock> fees base&ppm to zero 0 ? 13:12 < m-schmoock> other than these final adjustments its more or less ready 13:21 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.3] 13:29 < t0mix> hmm.. when I tried "pay" with c-lightning and keep "top" running, I see lightning_gossipd going to 100% CPU consumption. .. can it be that rapsberry pi is simply too slow CPU for fast process of "pay" command? 13:31 < m-schmoock> routing module is expensive I guess 13:32 < t0mix> if that's the case, then I have finaly an excuse to buy more powerfull server :) 13:33 < m-schmoock> you need a donation? 13:33 < t0mix> oh, no.. thank you <3 13:33 < m-schmoock> if your budged was limited to raspi :D 13:34 < t0mix> no, I just don't like to throw money away if there is no real reason 13:34 < m-schmoock> t0mix: I really think payment routing should pe possible on raspi without a noticable CPU loop 13:34 < t0mix> hmm.. 13:34 < m-schmoock> Im not that into routing yet though 13:35 < m-schmoock> can you do some tracing to check what the CPU is cycling the most? 13:35 < t0mix> strace? 13:37 < m-schmoock> I dont think syscalls will be very helpful, but you can give it a try 13:39 < t0mix> https://pastebin.com/PSyHFkW4 .. when you search for "!!!HERE!!!" string, you can see where it spends time waiting 13:39 < m-schmoock> maybe perf: http://www.brendangregg.com/perf.html 13:39 < t0mix> yes, I don't think it's helpful. I could use some debugging knowledge. 13:40 < m-schmoock> 5.4. User-Level Statically Defined Tracing (USDT) 13:41 < m-schmoock> okay thats interesting 13:41 < m-schmoock> shouldnt be CPU intense to read 13:41 < m-schmoock> it is asking its peer for a payment routing 13:41 < m-schmoock> is your c-light peered to 'slow' nodes? 13:41 < t0mix> how could I know 13:42 < m-schmoock> you told that LND seems faster, is your LND connected to other nodes? 13:42 < m-schmoock> becuase it does not look like the delay is caused by clightning but by remote peer 13:43 < t0mix> oh, no. I don't have LND running. it's only when I send payments from lightningspin.com to my c-lightning, it is almost instant 13:44 < t0mix> that is node named "lightning-roulette.com" 13:44 < m-schmoock> :D 13:44 < m-schmoock> love it 13:44 < t0mix> the game? 13:44 < m-schmoock> currently the most used lightning application ^^ 13:45 < t0mix> I love how fast the payments are from there. I hate game itself ^^ 13:45 < t0mix> lost about million on playing some time ago :) since then I use it only for tests (then I have excuse to play) 13:45 < m-schmoock> nvm, I doubt its a CPU isse at it takes most of the time to read from remote peer to do the stuff. long polling 13:46 < m-schmoock> their node seems better connected to you, probably dirctly 13:46 < m-schmoock> the other direction may be something completely different setup 13:46 < t0mix> oh yes, I am directly connected. which makes it even more weird that it takes so long 13:46 < m-schmoock> get your outbound channels fixed :D 13:46 < t0mix> I have channel opened with them 13:46 < m-schmoock> oh aha 13:47 < m-schmoock> maybe they want to earn on interest rates on finex or bitmex within that second 13:47 < m-schmoock> ^^ 13:47 < m-schmoock> btw, how long is 'long' ? 13:47 < t0mix> ok.. let me play one more spin =D 13:48 < m-schmoock> theres a special place in hell 13:48 < t0mix> time shows "real 0m14.477s" 13:48 < m-schmoock> joa 13:48 < m-schmoock> nice slow 13:48 < t0mix> and I lost 13:48 < m-schmoock> keeps you from gambling too much 13:48 < m-schmoock> i noticed slow payments as well, but not to all destinations 13:49 < m-schmoock> the current codebase lacks features to clean channels based on response behaviour and such 13:51 < t0mix> I wish I knew where to search to troubleshoot 13:53 < m-schmoock> do a "lightning-cli listforwards" 13:53 < t0mix> that is fast 13:53 < m-schmoock> the last entry should be your slow pay 13:53 < m-schmoock> identify the channel and maybe close it 13:53 < m-schmoock> to force you node to use another one 13:53 < t0mix> no, in forwards, there are only payments that passed through. not the one initiated by me. 13:53 < m-schmoock> uhm, yes 13:53 < m-schmoock> nvm, you tolk you have a direct connectoin 13:54 < m-schmoock> so this shouldnt help 13:55 < t0mix> let's say you want to spin a wheel (just for a science), here is an invoice: lnbc10u1pwxk2v8pp5zapwqlh4ngk430sjvrraxdjynkwdh3m93gqr87k4m7kfxktwaxmsdqlxycrqvpqwdshgueqvfjhggr0dcsrx7qcqzysrzjqd20ek03248n2pfr3cdnc2fz8p5f2descv9k2eddfqkux85shnafxzykpgqqy2cqqyqqqqlgqqqqqqgqjq6r9v98z276lpfl6zr5hc3qecsylzzvkrzn2gp5gccxwe03t945th5x99peda0t0sjhqx2us5glrmx83hkllk3u6s5lqanwm24w5v97qpgrr5am 13:55 < t0mix> when you do decodepay and try "lightning-cli getroute "0354fcd9f1554f3505238e1b3c29223868953730c30b6565ad482dc31e90bcfa93" 1000000 9 9" .. how long it takes for you to complete? 13:56 < t0mix> when I try, it complete in 12 seconds, and selected 4 hops route =| 13:57 < m-schmoock> 0.5 seconds 13:57 < m-schmoock> 3 hops 13:57 < t0mix> and you don't even have direct channel 13:57 < t0mix> something is wrong.. terribly wrong 13:58 < m-schmoock> but I have a i7 quadcode hyperthreaded 13:58 < t0mix> with my installation at least. I guess you don't run on raspberry 13:58 < m-schmoock> not really no 13:58 < m-schmoock> CPU time was 4 milliseconds 13:58 < m-schmoock> and 580 millis for reading remote sockets 13:59 < t0mix> how did you measure? 13:59 < m-schmoock> jsut time 13:59 < m-schmoock> tells you real and user 13:59 < m-schmoock> the delta is interrupt read 13:59 < m-schmoock> and my ssd is fast, so only network reamins as bottleneck 14:00 < t0mix> for me it was 0.001s user, 0.01s sys .. 12.256 real 14:00 < m-schmoock> 4 hops... what does the 'delay' param tell you in the route? 14:00 < m-schmoock> is there a very slow one ? 14:01 < m-schmoock> or are all slow 14:01 < m-schmoock> not shure though if 'delay' means wht i think it means in this context 14:01 < t0mix> is not delay only to tell me how many blocks to wait in case that node on route goes down..just in moment when my payment went into? 14:01 < t0mix> I think delay is what I just described 14:01 < m-schmoock> aha :D nailed it 14:02 < m-schmoock> uhm, we should include a response time or something 14:02 < m-schmoock> we can ask some smarter people tomorrow maybe 14:02 < m-schmoock> maybe there is a ping echo function in the RPC interface 14:03 < m-schmoock> so you can ping all the hops an see if theres one slow 14:04 < t0mix> ok.. I just run ping test to all peers I'm connected to 14:04 < m-schmoock> lol 14:04 < t0mix> although, not everyone respond to ping 14:04 < m-schmoock> some people disallow ping, bt you can try 14:04 < m-schmoock> .. 14:05 < t0mix> yes, I do disallow, too 14:05 < m-schmoock> sneaky 14:05 < t0mix> yeah, I'm invisible on internet. 3000+ attempts to break into my server within last week :) 14:05 < m-schmoock> i just ignore it, this is normal 14:06 < m-schmoock> I think identifying slow channels (not connected to you directly) is a interesting topic 14:06 < t0mix> I ignore it, too. I was just worried if so many attempts are not too much for my poor raspberry =D but it seems fine with it. 14:06 < m-schmoock> sure some folks are working on it 14:07 < t0mix> ok, so I have results of ping 14:07 < m-schmoock> like performance check payments of some milli-sats 14:07 < t0mix> those who replied were in range 20-120ms .. it's not bad 14:07 < m-schmoock> now you need to construct own route and to small test payments for each hop 14:07 < m-schmoock> there is a very slow one in between 14:07 < m-schmoock> topic in itself 14:08 < t0mix> still, I think that route selection itself is somehow messed. why it even choose 4 hops route when I do have direct channel? 14:08 < m-schmoock> being sneaky? 14:08 < m-schmoock> :D 14:08 < t0mix> lol 14:57 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 15:02 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 15:53 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 16:05 < rusty> t0mix: what version? In master you can use 'paystatus ' to see exactly what it tried to do? 16:33 -!- kexkey [~kexkey@87.101.92.74] has quit [Quit: Scaling pentatonically] 17:51 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 17:52 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Client Quit] 18:19 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 18:55 -!- born2tinkr [~Adium@2600-6c40-6000-0c60-ecf0-a5c7-ea16-07c9.dhcp6.chtrptr.net] has joined #c-lightning 19:09 -!- born2tinkr [~Adium@2600-6c40-6000-0c60-ecf0-a5c7-ea16-07c9.dhcp6.chtrptr.net] has left #c-lightning [] 20:12 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 20:17 -!- kexkey [~kexkey@87.101.92.74] has joined #c-lightning 20:24 -!- kexkey [~kexkey@87.101.92.74] has quit [Ping timeout: 246 seconds] 20:45 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 21:29 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds] 21:29 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 21:38 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds] 21:40 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 21:47 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has left #c-lightning [] 21:47 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has joined #c-lightning 22:06 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning 22:52 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 258 seconds] 22:52 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning --- Log closed Tue Feb 19 00:00:54 2019