--- Day changed Sun May 06 2018
00:59 -!- lnostdal [~lnostdal@85.118.83.96] has quit [Ping timeout: 268 seconds]     
01:57 -!- lnostdal [~lnostdal@85.118.83.96] has joined #joinmarket     
02:38 -!- lnostdal [~lnostdal@85.118.83.96] has quit [Ping timeout: 260 seconds]     
05:02 -!- takamatsu [~takamatsu@unaffiliated/takamatsu] has joined #joinmarket     
05:23 -!- takamatsu [~takamatsu@unaffiliated/takamatsu] has quit [Ping timeout: 264 seconds]     
05:37 -!- takamatsu [~takamatsu@unaffiliated/takamatsu] has joined #joinmarket     
08:40 -!- GitHub160 [GitHub160@gateway/service/github.com/x-zocqhiithljxodui] has joined #joinmarket     
08:40 < GitHub160> [joinmarket-clientserver] jameshilliard opened pull request #140: Alternative approach to connection reset. (master...conn-reset) https://git.io/vprgS
08:40 -!- GitHub160 [GitHub160@gateway/service/github.com/x-zocqhiithljxodui] has left #joinmarket []     
09:33 < Lightsword> so…I was hitting this error https://github.com/JoinMarket-Org/joinmarket-clientserver/issues/125 and seems my last connection reset method wasn’t working but this seems to work ok https://github.com/JoinMarket-Org/joinmarket-clientserver/pull/140
10:07 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has quit [Ping timeout: 276 seconds]     
11:08 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 255 seconds]     
11:12 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #joinmarket     
13:00 < waxwing> Lightsword, yeah the bot told us :) (well that and notifications)
13:01 < waxwing> i'm loth to make comments as i've never experienced this condition even once. i can't remember what i did last time, i think i might have artificially triggered disconnect in regtest to see it happen.
13:02 < waxwing> but that isn't really that interesting, i guess just a sanity check. is there anyone else who has seen this problem happen to them live?
13:17 < waxwing> seeing pretty healthy traffic this weekend. also mempool grew a little bit recently.
13:50 < Lightsword> waxwing, there was a bug report that someone else made, I found it after I noticed the error
13:50 < Lightsword> waxwing, bug seems to mostly happen on OSX btw
13:51 < Lightsword> the other fix I did before wasn’t working for some reason
13:51 < Lightsword> but I confirmed this one logs “Connection was reset, attempting reconnect.” and succesfully reconnects afterwards
13:52 < Lightsword> I think it’s probably a quirk in the OSX TCP stack or something else in how keep alives are handled in OSX
13:56 < Lightsword> waxwing, btw this isn’t just an occasional error on OSX, it’s very frequent(effectively 100% occurance if bitcoind connection is idle for any non-trivial amount of time) and effectively completely breaks yield generators if reconnect doesn’t work
13:57 < waxwing> Lightsword, thanks, i was entirely unaware of it being on OSX, have reopened and commented that.
13:57 < waxwing> (maybe you mentioned and i just forgot)
13:58 < Lightsword> I probably didn’t since I originally thought it was not OSX specific
13:58 < waxwing> right. so let us know if it fixes it; thanks.
13:59 < Lightsword> oh, my PR fixed it for me on OSX
14:29 < waxwing> thanks
14:54 -!- Netsplit over, joins: Giszmo, takamatsu, gmaxwell
14:54 -!- takamatsu [~takamatsu@unaffiliated/takamatsu] has quit [Max SendQ exceeded]     
14:58 < waxwing> arubi, do you consider #135 ready? you seem to be saying it waits 60 seconds, that's gonna hurt if so.
14:58 < waxwing> also, why didn't #140 trigger travis i wonder
20:55 -!- AgoraRelay [~jmrelayfn@p5486674F.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds]     
21:07 -!- AgoraRelay [~jmrelayfn@p5DE4A8DA.dip0.t-ipconnect.de] has joined #joinmarket     
21:37 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit []