Fred Akalin
Fred Akalin
Ugh, this fix is buggy. Stay tuned...
Okay, this version should work. That's what I get for not testing before pushing...
go-spew, which testify uses, explicitly handles unexported fields; see https://github.com/davecgh/go-spew. So you're probably right in that the bug doesn't lie with testify directly. Perhaps it needs to revendor go-spew to...
I'm not tied to the b2-specific checksum validation. I think we do need some sort of retry on checksum failure during check (not sure if that currently happens during restore?),...
That error is when the number of data shards is >256, which is a par2 limitation. I suspect it has to do with the default block size not being intelligently...
I'll keep this open as a reminder to do calculate the parameters a bit more intelligently. The snippet you posted looks plausible, I assume you're gonna calculate that in your...
Ah, yes you're right! Forgot there was a smaller limit for data shards.
Yeah I don't think there's any real need to implement par2cmdline's computation exactly -- in fact, it seems pretty ad hoc, and I think if I think about it for...
Looking at the par spec, it looks like 'unicode' filenames are supported via a separate packet type: http://parchive.sourceforge.net/docs/specifications/parity-volume-spec/article-spec.html#i__134603784_1221 I'm definitely open to supporting utf8. can you give an example case...
I'll try to look at it this weekend! I don't know how much time I have for gopar coding these days, though... :(