--- Day changed Mon Sep 16 2019
00:32 -!- Vladimir65Nitzsc [~Vladimir6@ns334669.ip-5-196-64.eu] has joined #joinmarket     
03:32 -!- MaxSan [~four@185.156.175.35] has joined #joinmarket     
04:01 -!- MaxSan [~four@185.156.175.35] has quit [Ping timeout: 240 seconds]     
04:32 -!- MaxSan [~four@185.156.175.35] has joined #joinmarket     
05:42 -!- MaxSan [~four@185.156.175.35] has quit [Ping timeout: 265 seconds]     
07:00 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #joinmarket     
08:10 -!- viasil [~viasil@95.174.67.204] has quit [Ping timeout: 245 seconds]     
08:15 -!- viasil [~viasil@95.174.67.204] has joined #joinmarket     
08:24 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 245 seconds]     
08:28 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #joinmarket     
12:50 < arubi> takinbo, sorry I'm only now near the keyboard.  for some reason it seems that travis doesn't actually run the dockers even with the string in the commit message..  I can't look into it at the moment but maybe you could get them to run by removing the line in .travis.yml (maybe on a temporary branch in your github repo).  I'm home tomorrow so will go over your new additions
12:52 < takinbo> sounds good. i was also curious as to how it wasn't building and running the test for the dockers despite the commit message.
17:49 -!- AgoraRelay [~jmrelayfn@p5DE4A957.dip0.t-ipconnect.de] has quit [Ping timeout: 276 seconds]     
17:49 -!- CgRelayBot [~CgRelayBo@p5DE4A957.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]     
17:59 -!- CgRelayBot [~CgRelayBo@p5DE4A837.dip0.t-ipconnect.de] has joined #joinmarket     
18:01 -!- AgoraRelay [~jmrelayfn@p5DE4A837.dip0.t-ipconnect.de] has joined #joinmarket     
18:01 < fiatjaf> is it normal for people to joinmarket as their primary wallet?
18:05 -!- Vladimir65Nitzsc [~Vladimir6@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 240 seconds]     
18:39 < fiatjaf> I kinda want to make an http server + mobile interface to be able to send simple coinjoin transactions when on the go.
18:43 -!- technonerd [~techno@gateway/tor-sasl/technonerd] has quit [Ping timeout: 260 seconds]     
18:57 -!- technonerd [~techno@gateway/tor-sasl/technonerd] has joined #joinmarket     
19:22 -!- M1 [~Michail@michail.com] has quit [Ping timeout: 240 seconds]     
19:24 -!- M1 [~Michail@michail.com] has joined #joinmarket     
19:33 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has quit [Ping timeout: 276 seconds]     
19:39 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has joined #joinmarket     
20:44 -!- fishguts [~fishguts@121-200-12-43.79c80c.syd.nbn.aussiebb.net] has quit [Ping timeout: 264 seconds]     
20:54 -!- joinmarketuser [~joinmarke@193.37.252.131] has joined #joinmarket     
20:55 < joinmarketuser> hello - I got this error during tumble.py https://pastebin.com/Hnm7WDNY
20:56 < joinmarketuser> after that it just said stall detected then attempting to reconnect but never kept going, just seemed stuck
20:58 < joinmarketuser> wondering how to avoid the error but also is there a way i can continue tumble.py from where it was? i killed the stuck process
21:19 < takinbo> fiatjaf: sounds like a great idea; i see no reason why you can't use it as your primary wallet if there's a reasonable interface to go with it
21:22 < joinmarketuser> how do I use --restart?
21:24 < takinbo> joinmarketuser: you don't have to restart the process if tumbler.py stops. simply run the command again with all the parameter you specified during the initial run and it would continue from where it stopped. 
21:25 < joinmarketuser> @takinbo thank you. it basically got stuck and i killed it. I see in the help there is a --restart option. do I not need to specify that
21:26 < joinmarketuser> when would that flag be used 
21:26 < takinbo> you don't unless you want to start the process all over from the beginning which is probably not what you want to do
21:27 < joinmarketuser>   --restart             Restarts the schedule currently found in the schedule
21:27 < joinmarketuser>                         file in the logs directory, with name TUMBLE.schedule
21:27 < joinmarketuser>                         or what is set in the schedulefile option.
21:27 < takinbo> sorry maybe i have it backwards, that may be what you want to do. 
21:28 < takinbo> i think the `--restart` option is what does what i described. 
21:28 < joinmarketuser> thank you
21:29 < takinbo> you're welcome
21:30 < joinmarketuser> do you know if there is a difference between tumble.py and the gui option to "generate schedule" with defaults - do they behave the same
21:32 < takinbo> there's no difference; they are essentially the same. you could generate the schedule with the gui and continue with `tumbler.py`
21:58 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has quit [Ping timeout: 265 seconds]     
22:40 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has joined #joinmarket     
22:57 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has quit [Ping timeout: 245 seconds]     
23:12 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has joined #joinmarket