--- Day changed Mon Nov 04 2019
08:37 < adiabat> yeah I'm editing your add-resume-for-parseblock branch now
08:37 < adiabat> kindof changing a lot, hope you don't mind :)  but hopefully will get it to work.  then can update roadmap stuff
13:54 < adiabat> kcalvinalvin: I don't think I have write access to your github branches (or I set it up wrong and that's the error it gave me)
13:54 < adiabat> I pushed my changes to https://github.com/mit-dci/utreexo/tree/add-resume-for-parseblock
13:57 < adiabat> it seems to work and is fairly quick / efficient.  It still has a problem on one of my blocks folders though
14:01 < adiabat> it hits a dead end sometimes
14:02 < adiabat> I think the reason is that if you break where it's still got blocks from the previous file in ram (nextMap) those get lost and won't be read back
14:03 < adiabat> hm.  I think I know a quick / ugly way to fix that.  Only write to disk when nextMap is empty...
14:05 < adiabat> for example. there are two files.  file1: [1, 2, 6, 3] file2: [4, 5, 7, 8]
14:05 < adiabat> it gets to file2, and writes block 4, the the user exits
14:06 < adiabat> it loads back up to block2, writes 5, but then gets stuck on 7 because 6 wasn't read on the next execution
14:06 < adiabat> question is does nextMap *ever* get empty; if not that idea won't work.  will try
14:09 < adiabat> yeah ok the map is never empty so that idea's not going to work.  bleh.
14:18 < adiabat> also I think it doesn't wait for the waitGroups when it gets the sig; it just does os.Exit(1) which doesn't wait?
14:18 < adiabat> so maybe the DB is all messed up, haven't checked
14:57 < adiabat> man... why do they write the blocks folder in randomized order, serrrrriously.... 
14:57 < adiabat> anyway I have some ideas on how to fix this but none are super quick.  also we need to be able to catch the ctrl-c and clean up a bit before exiting
14:58 < adiabat> then can flush progress to disk only when quitting.  then could flush a lot more, like all the hashes of what's in the nextMap
20:38 < adiabat> OK so toomorrow (Tuesday) 9 am EST call?  Or 10 am EST?  (I can only do 30min long call if at 10 am)
20:39 < adiabat> I'll be online at 9am ( in 9h21m ) for the call, but if that's an hour too early will do it in 10h21m
21:50 < kcalvinalvin> 9am EST is infe
21:57 < kcalvinalvin> Yea... the branch doesn't really work at the moment. Thought it did :/
22:37 -!- instagibbs [~instagibb@pool-71-178-191-230.washdc.fios.verizon.net] has quit [Ping timeout: 276 seconds]     
22:49 -!- instagibbs [~instagibb@pool-71-178-191-230.washdc.fios.verizon.net] has joined #utreexo