--- Log opened Wed Oct 14 00:00:47 2020
09:40 -!- rjected [~dan@pool-151-203-65-159.bstnma.fios.verizon.net] has joined #utreexo
12:19 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #utreexo
12:22 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 246 seconds]
12:22 -!- belcher_ is now known as belcher
14:13 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 240 seconds]
14:18 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #utreexo
14:30 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 240 seconds]
14:41 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #utreexo
21:05 < adiabat> yes.  It's a fun combination of 2 off-by-1 errors
21:05 < adiabat> because blocks start at 1
21:08 < adiabat> and offset files always start at 0, or like, the first entry in any offset file is useless
21:24 < adiabat> also file.Seek() doesn't do what it says it does... blarg.
21:28 < adiabat> ok well there's some other error but finally got that one... ugh
21:29 < adiabat> file.Seek(offset int64, whence int)... supposedly returns (ret int64, err error)
21:29 < adiabat> say there's a file that's 32 bytes long.  And you say to seek to byte 64
21:29 < adiabat> it will return 64, and no error, and seek to byte 32
21:30 < adiabat> why no error?  Wouldn't "hey you tried to seek past the end of the file" be an error?  blah anyway that's how it does it
--- Log closed Thu Oct 15 00:00:47 2020