--- Day changed Sat Nov 03 2018 00:37 -!- melvster [~melvin@ip-86-49-18-46.net.upcbroadband.cz] has joined #lnd 00:53 -!- rhavar [uid237883@gateway/web/irccloud.com/x-jvwabjdxsldlsehy] has quit [Quit: Connection closed for inactivity] 01:05 -!- bitconner [~conner@c-73-170-56-77.hsd1.ca.comcast.net] has joined #lnd 01:09 -!- bitconner [~conner@c-73-170-56-77.hsd1.ca.comcast.net] has quit [Ping timeout: 252 seconds] 01:59 -!- lndbot [~lndbot@138.197.213.35] has quit [Remote host closed the connection] 01:59 -!- lndbot1 [~lndbot@138.197.213.35] has joined #lnd 02:13 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 02:20 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd 02:39 -!- RusAlex [~Chel@unaffiliated/rusalex] has quit [Ping timeout: 244 seconds] 02:42 -!- RusAlex [~Chel@unaffiliated/rusalex] has joined #lnd 02:44 -!- CryptoSigmund [~CryptoSig@ppp-88-217-106-141.dynamic.mnet-online.de] has joined #lnd 03:08 < Talkless> Hi, how could I debug payment timeouts? I get "[ERR] CRTR: Attempt to send payment a42d0438... failed: TemporaryChannelFailure(update=(*lnwire.ChannelUpdate)(0x14b28900)({ 03:08 < Talkless> I have 3 outgoing channels, and try to pay only ~50k satoshis, and it timeouts after 1 minute 03:09 < Talkless> all channels are active 03:11 < Talkless> queryroutes shows 10 routes 03:12 < Talkless> i'm running vanilla 0.5 lnd 03:18 -!- Beast [~quassel@222.109.180.10] has quit [Quit: No Ping reply in 180 seconds.] 03:19 -!- Beast [~quassel@222.109.180.10] has joined #lnd 03:22 < molz> Talkless, roasbeef explained this in an issue on GH: "TemporaryChannelFailure means that (likely the final) route attempted didn't have enough available channel bandwidth. It's an in-protocol error and not indicative of a bug" 03:23 < molz> https://github.com/lightningnetwork/lnd/issues/1044#issuecomment-379500638 03:23 < Talkless> "channel bandwith" ? 03:23 -!- RusAlex [~Chel@unaffiliated/rusalex] has quit [Quit: WeeChat 2.0.1] 03:24 < Talkless> welp, it is actually bitrefill it is receiving. 03:25 < molz> liquidity 03:26 < molz> "TemporaryChannelFailure is protocol level error. It means that along an HTLC route, a channel didn't have enough available bandwidth to carry the HTLC. The error returned is simply one of the last errors we encounter. For example, if hodlmoney doesn't have sufficient inbound payment bandwidth, then you won't be able to pay them no matter how many paths are shown. " 03:26 < molz> https://github.com/lightningnetwork/lnd/issues/1242#issuecomment-388591474 03:26 < molz> maybe update to the latest master? 03:28 < Talkless> maybe I'll try 03:29 < Talkless> Now I get "payment is in transition", because payment hanged, and more than a minute, did ctrl + c for "payinvoice", now doing another payment gives "payment in transition" 03:30 < Talkless> I've restarted lnd to try again, and after restart payment hanged and new payment attemnt prints "payment is in transition" 03:30 < molz> i wouldn't try again or the payment might get stuck 03:30 < Talkless> molz: that comment speaks about 0.4.x, I have 0.5 03:30 < Talkless> though of course I could try master. 03:31 < molz> 0.5 still had many bugs and they were fixed in later commits 03:31 < Talkless> yeah of course 03:33 < Talkless> molz: how do you normally upgrade lnd? git pull & install? I always get errors in this way, I just delete gopath and install from scratch. 03:34 < Talkless> or is there a "correct" way to udpate go applications? 03:34 < molz> git fetch 03:34 < molz> git checkout origin/master 03:34 < molz> make && make install 03:34 < molz> if make has an error about vendor then: make clean 03:34 < Talkless> yeam but during install I always get some sort depencewy issues 03:35 < Talkless> oh yea I guess it's that vendor 03:35 < Talkless> thanks molz, I'll try 03:35 < molz> 👍 03:49 -!- Beast [~quassel@222.109.180.10] has quit [Quit: No Ping reply in 180 seconds.] 03:51 -!- Beast [~quassel@222.109.180.10] has joined #lnd 03:56 -!- RusAlex [~Chel@unaffiliated/rusalex] has joined #lnd 03:58 < Talkless> molz: looks like "payinvoice" hang forever (now 10m. and counting) if performed just after lnd restart, even on latest master. 03:58 < Talkless> bitrefill payment will expire in few minutes, and there's still no timeout on lncli side 03:59 < molz> hm 03:59 < molz> then i guess def there's no route to your node 04:00 < molz> between your node and bitrefill 04:00 < molz> this happened to me also (with my clightning node) 04:01 < Talkless> if there's no route I get timeout in a minute or so 04:01 < Talkless> now it seems lncli is hanged forever (so far) 04:08 < molz> Talkless, is it still hanging? 04:08 < Talkless> yep, writing bug report 04:09 < Talkless> it's ~20 minutes now 04:09 < molz> i think you have to terminate it 04:09 < Talkless> molz: what log keys shoud I grep, what's relevant for payments? 04:09 < Talkless> I mean these four-word keys 04:10 < molz> i wish the software could say something like "there's no route, Joe, don't do this again" lol 04:10 < molz> oh i normally would terminate a hanging process with Ctrl+C 04:14 < Talkless> yeah, errors could be more descriptive 04:17 < Veggen> I have had hanging payments fulfill after 10 minutes... 04:17 < Veggen> it happens. there's a reason it's not declared a failure yet :) 04:33 < Talkless> molz: https://github.com/lightningnetwork/lnd/issues/2141 04:33 < Talkless> Veggen: payment receiver would expire invoice afte 15 mintues, that's dangerous or at least inconveniet, with all refund & stuff... 04:36 < molz> Talkless, cool... i hope we could get some other solution for this 04:38 < molz> i know it sucks when we can't find a route, but i also know we're still in early days with this tech 04:45 < Talkless> molz: I understand that completely :) 04:45 < Talkless> but I *will not* open direct channel to receiver, privacy ftw :)) 04:46 < Talkless> HTLC rules :D 04:49 < molz> Talkless, sure, i understand 04:50 < Talkless> Well, I would, with friends for example, to pay each other for common expenses, etc. 04:50 < Talkless> when mobile apps will allow receiveing.. 04:50 < molz> but even with a direct channel, the merchant still doesn't know for sure it's from you 04:51 < Talkless> I was sure that thers'e no onion routing with direct channel. Are you sure about that? 04:53 < Veggen> hmmm...it's no different? for sure he gets only the innermost layer, but he can't know whether or not you peeled off something? 05:01 < Talkless> I was reading somewhere that thes is no onlio at all, just channel update, as you update channel balances due to TX fees. But I could be mixing something. 05:01 < Talkless> no onion at all* 05:45 < molz> Talkless, what do you think of this suggestion from alex b.: https://twitter.com/alexbosworth/status/1057653571821301761 05:51 -!- slivera_ [slivera@gateway/vpn/privateinternetaccess/slivera] has quit [Ping timeout: 268 seconds] 06:17 < Talkless> molz: sorry I am not sure if I understand it. 06:18 -!- booyah_ is now known as booyah 06:20 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood] 06:21 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lnd 06:22 -!- mp___ [~mp@hell.cx] has joined #lnd 06:22 -!- mp___ [~mp@hell.cx] has quit [Remote host closed the connection] 06:25 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 06:26 -!- mp___ [~mp@hell.cx] has joined #lnd 06:26 -!- mp___ [~mp@hell.cx] has quit [Remote host closed the connection] 06:26 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #lnd 06:27 < molz> Talkless, i'm not quite sure either, maybe @alexbosworth can explain when he wakes up? :) 06:28 < molz> currently if a HTLC payment can't go thru and gets stuck in a channel, it times out after some blocks and the amount is released, unless the software has a bug like what happened to my HTLC payment (on clightning node and got solved) 06:28 -!- mp___ [~mp@hell.cx] has joined #lnd 06:28 -!- mp___ [~mp@hell.cx] has quit [Remote host closed the connection] 06:30 -!- mp___ [~mp@hell.cx] has joined #lnd 06:30 -!- mp___ [~mp@hell.cx] has quit [Remote host closed the connection] 06:31 -!- mp [sid298319@gateway/web/irccloud.com/x-iewhohiofkzqbigr] has joined #lnd 06:33 < molz> Talkless, btw, have you checked to see if your payment got stuck ? 06:33 < Talkless> I still have lncli running :) 06:34 < molz> wut 06:34 < Talkless> I don't see it among listpayments 06:34 < Talkless> I guest it just deadlocker or whatever 06:34 < molz> Ctrl+C can't help? 06:35 < Talkless> no I don't want to kill it right now, maybe some one will ask for some diagnostics, backtrace or something. 06:35 < Talkless> I am in no rush. 06:37 < molz> that you can get in the logs 06:38 < molz> and i think it already tells you in the log why it's hanging 06:38 -!- aielima [~aielima@gateway/tor-sasl/aielima] has joined #lnd 06:38 < molz> can't get blood out of a turnip, if there's no route/liquidity/bandwidth then it just can't happen, can't force any node to do it 06:40 < Veggen> but these hanging calls are worse than failures. 06:40 < Veggen> hope it'll get better at some point :) 06:46 < molz> yea 06:50 < Veggen> If you have recently updated node software, I don't really understand why it'd happen. Either your node can forward it, or it can't. So there's bad nodes on the way. 06:52 < Veggen> question is: can we distinguish between bugs and malice, in the future? We need to not have to rely on not passing by malicious nodes, or at least be able to learn from it so that we don't use that node the next time. 06:52 < Talkless> uhg, looks like my lnd decided to force-close channel with Joltfun :( "unable to accept new commitment: rejected commitment: commit_height=662, invalid_commit_sig=" 06:55 < Talkless> looks like this: https://github.com/lightningnetwork/lnd/issues/1908 06:59 < molz> they might need more log from you, Talkless 07:00 < Talkless> gerrping channel point I don't see anything more interesting 07:04 < Talkless> greping * 07:05 -!- bitconner [~conner@c-73-170-56-77.hsd1.ca.comcast.net] has joined #lnd 07:09 < molz> im wondering if this hanging payment forces the channel to be settled onchain 07:09 < Talkless> could be 07:09 -!- bitconner [~conner@c-73-170-56-77.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds] 07:10 < Talkless> or simply because I've upgraded to master, and other node failed to communicate properly with mine 07:10 < molz> no 07:10 < molz> did you have only one channel ? 07:12 < molz> roasbeef, lnd faucet is down? 07:16 -!- deusexbeer [~deusexbee@080-250-075-178-dynamic-pool-adsl.wbt.ru] has quit [Quit: Konversation terminated!] 07:26 -!- mp___ [~mp@hell.cx] has joined #lnd 07:26 -!- mp___ [~mp@hell.cx] has quit [Remote host closed the connection] 07:34 < Talkless> molz: I had 4 channels, 3 outgoing (to Joltfun too), and one incomming 07:43 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #lnd 07:46 -!- mp___ [~mp@hell.cx] has joined #lnd 07:46 -!- mp___ [~mp@hell.cx] has quit [Remote host closed the connection] 07:49 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 07:49 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #lnd 08:01 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has joined #lnd 08:21 < molz> Talkless, hm why 3 channel to joltfun but can't send a payment to bitrefill, im wondering 08:22 < Talkless> yes that was strange 08:22 < molz> Talkless, and it seems joltfun has 3 nodes but only this one is a good one: 0374ecf61ed6c1208c42339f47decde2bc0c4393ac95f07827b3471e939d7eb961 08:22 < Talkless> 037.. that's the one i've used, and it's forced-closed now :( 08:22 < molz> Talkless, did you have all 3 channels to that node? 08:23 < Talkless> this channel did work for a long time, and after todays failure to pay to bitrefill, and after upgrade to master, it was closed. 08:23 < Talkless> I stil lbelieve it's incompatibility due to latest master :) 08:23 < Talkless> speaking of closure. 08:23 < Talkless> molz: no, one 08:23 < Talkless> just one to joltfun 08:23 < Talkless> and some autopilot-random once to others 08:32 -!- deusexbeer [~deusexbee@080-250-075-178-dynamic-pool-adsl.wbt.ru] has joined #lnd 09:26 -!- mp___ [mp@hell.cx] has joined #lnd 09:26 -!- mp___ [mp@hell.cx] has quit [Remote host closed the connection] 09:50 -!- mp___ [mp@hell.cx] has joined #lnd 09:50 -!- mp___ [mp@hell.cx] has quit [Remote host closed the connection] 09:53 -!- mp___ [mp@hell.cx] has joined #lnd 09:53 -!- mp___ [mp@hell.cx] has quit [Remote host closed the connection] 10:02 -!- frib [~dynorsau@2601:585:8502:52b5:c0de:252f:9bc7:9025] has quit [Quit: Leaving] 10:28 -!- mp___ [mp@hell.cx] has joined #lnd 10:28 -!- mp___ [mp@hell.cx] has quit [Remote host closed the connection] 10:44 < Veggen> hrmf. I have 17 active channels. but a payment of 1200 satoshi is hanging... 10:47 < molz> hm i just sent a post and got disconnected, i guess the line didn't show? 10:47 < molz> Veggen, are any of those channels inactive? 10:48 < Veggen> correction: 16 *active* channels. 10:49 < Veggen> out of a total of 19. 10:50 < molz> in the past i've found many times the inactive channels were blockers for payments so i would close them and after that my payments could go thru 10:51 < Veggen> mrh. but should not be? inactive channels shouldn't be used for routing? 10:52 < Veggen> but okok. let me see what they are... 10:52 < molz> flapping nodes, inactive channels, unstable nodes... are big distractors and not helping LN 10:52 < Veggen> true, but in the end we'll have to cope with them :) 10:52 < molz> in the end, we need the software to be smarter 10:52 < Veggen> if it only works if everyone is running his node flawlessly, it's not going to work. 10:52 < Veggen> yup 10:53 < Veggen> so some issues now is going to pinpoint where we need to do work. 10:53 < molz> people are free to use shitty hardware and whatever, but the software should be able to avoid them 10:53 < Veggen> yes, of course. 10:53 < Veggen> that's what I'm saying. 10:56 < Veggen> nope, pubkey of inactive channels are not in lnd.log... 11:01 -!- deusexbeer [~deusexbee@080-250-075-178-dynamic-pool-adsl.wbt.ru] has quit [Quit: Konversation terminated!] 11:04 < molz> now we're going to have many private channels from mobile nodes... lnd should be able to know that right? 11:04 < molz> those aren't distractors because they're not routing nodes 11:04 -!- bitconner [~conner@c-73-170-56-77.hsd1.ca.comcast.net] has joined #lnd 11:09 -!- bitconner [~conner@c-73-170-56-77.hsd1.ca.comcast.net] has quit [Ping timeout: 252 seconds] 11:16 -!- Beast [~quassel@222.109.180.10] has quit [Ping timeout: 252 seconds] 11:18 -!- Beast [~quassel@222.109.180.10] has joined #lnd 12:26 -!- ChunkyPuffs [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has quit [Remote host closed the connection] 12:26 -!- aielima [~aielima@gateway/tor-sasl/aielima] has quit [Remote host closed the connection] 12:26 -!- aielima [~aielima@gateway/tor-sasl/aielima] has joined #lnd 12:26 -!- ChunkyPuffs [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has joined #lnd 12:28 -!- mp___ [mp@hell.cx] has joined #lnd 12:28 -!- mp___ [mp@hell.cx] has quit [Remote host closed the connection] 12:50 -!- ChunkyPuffs [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has quit [Remote host closed the connection] 12:50 -!- aielima [~aielima@gateway/tor-sasl/aielima] has quit [Remote host closed the connection] 13:39 -!- deusexbeer [~deusexbee@080-250-077-201-dynamic-pool-adsl.wbt.ru] has joined #lnd 14:05 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 14:07 -!- booyah [~bb@193.25.1.157] has joined #lnd 14:14 -!- aielima [~aielima@gateway/tor-sasl/aielima] has joined #lnd 14:23 -!- Veggen [~vegard@engen.priv.no] has quit [Ping timeout: 264 seconds] 14:23 -!- Veggen [~vegard@engen.priv.no] has joined #lnd 14:28 -!- mp___ [mp@hell.cx] has joined #lnd 14:28 -!- mp___ [mp@hell.cx] has quit [Remote host closed the connection] 15:02 -!- ziya [~ziya@85.195.123.26] has joined #lnd 15:04 < wpaulino> Talkless: the payment can hang if an intermediate node doesn't send a response back 15:04 < wpaulino> the timeout thing is weird atm, as it'll only apply between payment attempts 15:04 < ziya> hey guyz.. so I've been thinking.. what if merchants with high liquidity refuse to open channels with small businesses cuz the big hubs don't want to lock an amount of bitcoin with the small business in a channel cuz they're not sure if they'd benefit from relaying the small businesses' transactions (which are few and probably small) 15:04 < wpaulino> basically whenever you pay an invoice, a payment session is started where multiple attempts are tried until a terminal success or failure 15:05 < wpaulino> if the timeout happens in between attempts, then it'll fail saying it timed out 15:05 < wpaulino> otherwise if the paymet is stuck due to an intermediate node not responding, it'll hang 15:06 < wpaulino> since 0.5 i've noticed that this has become a pretty common problem (stuck htlcs) 15:06 < Talkless> wpaulino: I believe this was my first payment with 0.5 15:06 < wpaulino> we have a hunch towards what it is but haven't been able to really track it down as it's kinda hard to tell where it got stuck 15:06 < Talkless> at least I don't really recall others... 15:09 < wpaulino> Talkless: as for the rejected commitment issue, the default logging level unfortunately doesn't provide much info for us 15:09 < wpaulino> you'd need to run LNWL=trace, which can be pretty spammy 15:11 < wpaulino> Talkless: do you have any pending_htlcs showing in listchannels? 15:12 < Talkless> just a sec. 15:12 < Talkless> yes! the ammount I was sending to bitrefill 15:13 < wpaulino> just one? 15:13 < wpaulino> looking at your issue now, i see that you tried multiple invoices 15:13 < Talkless> yes I tried, but I see only one 15:14 < wpaulino> gotcha, possibly that some of them timed out already 15:14 < Talkless> can I see in the logs that it timouted? 15:14 < wpaulino> can you reproduce the high cpu usage reliably upon restarts? 15:14 < wpaulino> yeah 15:14 < wpaulino> it would force close the channel if it times out 15:16 < Talkless> wpaulino: yes as far as I remember, it's always like that. It fades after a day or more. 15:17 < wpaulino> Talkless: are you familiar with profiling go programs? 15:17 < Talkless> cpu usage that is. 15:17 < Talkless> nnope 15:17 < wpaulino> if it only happens on restarts, it's likely that nodes are just sending you their whole graph 15:17 < Talkless> i can launch perf top :) 15:24 < Talkless> wpaulino: this is perf recording for a minute: 15:24 < Talkless> https://paste.debian.net/1050264/ 15:28 < wpaulino> Talkless: unfortunately that doesn't provide much helpful info 15:28 < wpaulino> but i can guide how to get an appropriate profile if you have some time 15:29 -!- frib [~dynorsau@2601:585:8502:52b5:b919:bec0:f2eb:2d47] has joined #lnd 15:29 < Talkless> sorry wpaulino but it's a bit late already, I will go to sleep in no time :( 15:30 < wpaulino> Talkless: no worries, i'll post some instructions on the issue that you can follow on your own time 15:30 < Talkless> ok thanks wpaulino 15:31 < Talkless> thanks for all the work, bye! 15:31 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!] 15:54 -!- colua [b2269a3b@gateway/web/freenode/ip.178.38.154.59] has joined #lnd 16:26 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Ping timeout: 245 seconds] 16:28 -!- mp___ [mp@hell.cx] has joined #lnd 16:28 -!- mp___ [mp@hell.cx] has quit [Remote host closed the connection] 16:38 < colua> hi 16:39 < colua> Hi, I'm trying to install lnd following the tutorial https://ln-zap.github.io/zap-tutorials/iOS-remote-node-setup.html, but I get an error when I run zapconnect 16:39 < colua> lnd is successfully initialized! 16:39 < molz> can you run lnd without zap first to see if it's ok? 16:40 < colua> when executing the command "lnd", I get: 16:40 < colua> loadConfig: either bitcoin.active or litecoin.active must be set to 1 (true) 16:40 < colua> is that correct? 16:41 < molz> right, that's what it says 16:41 < molz> which chain are you trying to run lnd? 16:42 < colua> I'm afraid I don't know :-/ I'm just following the tuorial step by step 16:42 < colua> (I'm a newbie, as you might have guessed...) 16:43 < wpaulino> colua: what's the error you're seeing from zapconnect? 16:43 < molz> zap has a slack, can you ask them on their slack? 16:43 < colua> open /root/.lnd/lnd.conf: no such file or directory 16:43 < colua> open /root/.lnd/data/chain/bitcoin/mainnet/admin.macaroon: no such file or directory 16:43 < colua> also: when I run make in the zap-directory, I only get the following output: 16:44 < colua> go get ./... 16:44 < colua> go install -v ./... 16:44 < colua> that looks strange, no? 16:44 < colua> shouldn't there be more output? 16:45 < colua> @wpaulino: is slack a channel? 16:45 < wpaulino> no it's a separate chat app 16:45 < wpaulino> not familiar with zapconnect but it seems to be defaulting to the mainnet macaroon, while the guide is for testnet 16:46 < wpaulino> try this: zapconnect --adminmacaroonpath=/root/.lnd/data/chain/bitcoin/testnet/admin.macaroon 16:47 < colua> ok, I did. The first output line said "open /root/.lnd/lnd.conf: no such file or director", and after that the QR code is displayed :) 16:48 < wpaulino> yeah that's fine 16:48 < colua> so that seems to work then, even though it doesn't find lnd.conf!? is that no problem? 16:48 < wpaulino> just means a config file doesn't exist. it's not needed since you launced lnd with the flags instead 16:49 < colua> ok very cool, thanks wpaulino, I'll try to go on with the zap app then :) 16:51 -!- CryptoSigmund [~CryptoSig@ppp-88-217-106-141.dynamic.mnet-online.de] has quit [Read error: Connection reset by peer] 16:53 < colua> The QR code is ridiculously big though, and even with many ctrl-, it's still twice as high as my laptop screen, even though the width is half the screen size only. Doesn't the code have to be square?. 16:54 < colua> I ran the code again and now it's still huge, but at lease square... I'll gimp it smaller... 16:55 < molz> wow.. i'm just now looking at that zap link, it seems really cool 16:55 < molz> colua, are you running zap on your iphone? 16:56 < colua> i have installed it on testflight, now I have to connect it with the QR code 16:57 < colua> I have to reduce the code size first :o| 16:57 < wpaulino> colua: lol perhaps you should join their slack and let em know 16:58 < colua> I don't know what that means "join their slack" :/ 16:58 < molz> colua, you've never heard of "slack.com"? 17:00 < colua> eeeuh I guess have heard of it, but it's not something I use (yet)... I'm discovering 17:00 < colua> all this 17:02 < wpaulino> colua: there's a link here https://zap.jackmallers.com/ 17:04 < colua> Thanks :) I'm joining the Slack workspace Zap 17:16 <@roasbeef> faucet back now :) 17:18 < molz> thanks, roasbeef ! lol 17:19 <@roasbeef> Veggen: there's bit a bit of a spike lately w.r.t stuff like this recently, we fixed a bug that could inadvertnly cause lnd to stop reading new messages from peers, and have noticed issues attempting to route thru acinq lately 17:26 -!- colua [b2269a3b@gateway/web/freenode/ip.178.38.154.59] has quit [Quit: Page closed] 18:28 -!- mp___ [mp@hell.cx] has joined #lnd 18:28 -!- mp___ [mp@hell.cx] has quit [Remote host closed the connection] 18:32 -!- aielima [~aielima@gateway/tor-sasl/aielima] has quit [Remote host closed the connection] 19:00 -!- melvster [~melvin@ip-86-49-18-46.net.upcbroadband.cz] has quit [Ping timeout: 272 seconds] 19:04 -!- github-lnd [github-lnd@gateway/service/github.com/x-rjbgxrzmiypoxcws] has joined #lnd 19:04 -github-lnd:#lnd- [lnd] ErikEk opened pull request #2143: Improving color validation code (master...improv_color_validation) https://git.io/fxhrZ 19:04 -!- github-lnd [github-lnd@gateway/service/github.com/x-rjbgxrzmiypoxcws] has left #lnd [] 19:42 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 244 seconds] 19:44 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnd 19:53 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 20:00 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 20:28 -!- mp___ [mp@hell.cx] has joined #lnd 20:28 -!- mp___ [mp@hell.cx] has quit [Remote host closed the connection] 20:39 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Remote host closed the connection] 20:41 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Remote host closed the connection] 21:06 -!- ziya [~ziya@85.195.123.26] has quit [Ping timeout: 252 seconds] 21:50 -!- douglas__ [~douglas@c-24-34-137-83.hsd1.nh.comcast.net] has joined #lnd 21:53 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 21:57 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Remote host closed the connection] 22:28 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Read error: Connection reset by peer] 22:28 -!- mp___ [mp@hell.cx] has joined #lnd 22:28 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Read error: Connection reset by peer] 22:28 -!- aerth [~aerth@gateway/tor-sasl/aerth] has quit [Read error: Connection reset by peer] 22:28 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Read error: Connection reset by peer] 22:28 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Write error: Connection reset by peer] 22:28 -!- mp___ [mp@hell.cx] has quit [Remote host closed the connection] 22:28 -!- aerth [~aerth@gateway/tor-sasl/aerth] has joined #lnd 22:29 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #lnd 22:29 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnd 22:29 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #lnd 22:29 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #lnd 22:34 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 22:46 -!- valwal [~quassel@2601:645:8201:a6f8:f2d5:bfff:feea:f362] has joined #lnd 23:02 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 23:03 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Ping timeout: 245 seconds] 23:25 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 23:26 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #lnd 23:29 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 23:29 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #lnd 23:32 -!- tuxcanfly [~tuxcanfly@146.185.169.116] has quit [Ping timeout: 260 seconds] 23:32 -!- tuxcanfly [~tuxcanfly@146.185.169.116] has joined #lnd 23:38 -!- Talkless [~Talkless@hst-253-134.splius.lt] has joined #lnd